Re: [PATCH 2/2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: NeilBrown <neilb@xxxxxxxx>
Subject: Re: [PATCH 2/2] loop: Add PF_LESS_THROTTLE to block/loop device thread.
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 16 Jun 2017 00:36:58 -0700
Cc: Jens Axboe <axboe@xxxxxx>, linux-block@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <149758932925.10006.1411305319375332201.stgit@noble>
User-agent: Mutt/1.8.0 (2017-02-23)

why isn't loop using kthread_create_worker()?  Why isn't the less
throttle a flag to kthread_create_worker()?  I hate all this open
coding..

References:
- [PATCH 0/2] Two fixes for loop devices
  - From: NeilBrown
- [PATCH 2/2] loop: Add PF_LESS_THROTTLE to block/loop device thread.
  - From: NeilBrown

Prev by Date: Re: [PATCH 00/13] block: assorted cleanup for bio splitting and cloning.
Next by Date: Re: [PATCH 1/2] loop: use filp_close() rather than fput()
Previous by thread: [PATCH 2/2] loop: Add PF_LESS_THROTTLE to block/loop device thread.
Next by thread: Re: [PATCH 0/2] Two fixes for loop devices
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux