Re: blk-mq 5-8 times slower for bmap-tools

2018-08-22 Thread Ricardo Ribalda Delgado
Hi Ben On Wed, Aug 22, 2018 at 9:22 PM Ben Hutchings wrote: > > On Mon, 2018-08-20 at 11:04 +0200, Ricardo Ribalda Delgado wrote: > > Hello Ming > > On Mon, Aug 20, 2018 at 10:30 AM Ming Lei wrote: > [...] > > > One problem found from your iostat log is that looks there is ~30sec > > > idle perio

Re: blk-mq 5-8 times slower for bmap-tools

2018-08-22 Thread Ming Lei
On Thu, Aug 23, 2018 at 01:51:05AM +0100, Ben Hutchings wrote: > On Thu, 2018-08-23 at 06:02 +0800, Ming Lei wrote: > > On Wed, Aug 22, 2018 at 08:22:00PM +0100, Ben Hutchings wrote: > > > On Mon, 2018-08-20 at 11:04 +0200, Ricardo Ribalda Delgado wrote: > > > > Hello Ming > > > > On Mon, Aug 20, 2

Re: [PATCH blktests 0/3] Add NVMeOF multipath tests

2018-08-22 Thread Bart Van Assche
On Tue, 2018-08-21 at 08:46 +0200, Johannes Thumshirn wrote: > On Mon, Aug 20, 2018 at 03:46:45PM +, Bart Van Assche wrote: > > Moving these tests into the nvme directory is possible but will make it > > harder to run the NVMeOF multipath tests separately. Are you fine with this? > > Both way'

Re: blk-mq 5-8 times slower for bmap-tools

2018-08-22 Thread Ben Hutchings
On Thu, 2018-08-23 at 06:02 +0800, Ming Lei wrote: > On Wed, Aug 22, 2018 at 08:22:00PM +0100, Ben Hutchings wrote: > > On Mon, 2018-08-20 at 11:04 +0200, Ricardo Ribalda Delgado wrote: > > > Hello Ming > > > On Mon, Aug 20, 2018 at 10:30 AM Ming Lei wrote: > > > > [...] > > > > One problem found

Re: blk-mq 5-8 times slower for bmap-tools

2018-08-22 Thread Ming Lei
On Wed, Aug 22, 2018 at 08:22:00PM +0100, Ben Hutchings wrote: > On Mon, 2018-08-20 at 11:04 +0200, Ricardo Ribalda Delgado wrote: > > Hello Ming > > On Mon, Aug 20, 2018 at 10:30 AM Ming Lei wrote: > [...] > > > One problem found from your iostat log is that looks there is ~30sec > > > idle perio

Re: [GIT PULL] Follow up block changes for this merge window

2018-08-22 Thread Jens Axboe
On 8/22/18 2:39 PM, Linus Torvalds wrote: > On Wed, Aug 22, 2018 at 10:54 AM Jens Axboe wrote: >> >> - Set of bcache fixes and changes (Coly) > > Some of those bcache style fixes look questionable. > > Maybe we should push back on some of the checkpatch rules instead? > > Like having argument n

Re: [GIT PULL] Follow up block changes for this merge window

2018-08-22 Thread Linus Torvalds
On Wed, Aug 22, 2018 at 10:54 AM Jens Axboe wrote: > > - Set of bcache fixes and changes (Coly) Some of those bcache style fixes look questionable. Maybe we should push back on some of the checkpatch rules instead? Like having argument names in declarations - sometimes descriptive names can be

Re: [PATCH] blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait

2018-08-22 Thread Holger Hoffstätte
On 08/22/18 21:46, Jens Axboe wrote: On 8/22/18 1:37 PM, Holger Hoffstätte wrote: On 08/22/18 21:17, Jens Axboe wrote: So the obvious suspect is the new return of UINT_MAX from get_limit() to __wbt_wait(). I first suspected that I mispatched something, but it's all like in mainline or your tree

Re: [PATCH] blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait

2018-08-22 Thread Jens Axboe
On 8/22/18 1:37 PM, Holger Hoffstätte wrote: > On 08/22/18 21:17, Jens Axboe wrote: >>> So the obvious suspect is the new return of UINT_MAX from get_limit() to >>> __wbt_wait(). I first suspected that I mispatched something, but it's all >>> like in mainline or your tree. Even the recently moved-a

Re: [PATCH] blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait

2018-08-22 Thread Holger Hoffstätte
On 08/22/18 21:17, Jens Axboe wrote: So the obvious suspect is the new return of UINT_MAX from get_limit() to __wbt_wait(). I first suspected that I mispatched something, but it's all like in mainline or your tree. Even the recently moved-around atomic loop inside rq_wait_inc_below() is 1:1 the s

Re: blk-mq 5-8 times slower for bmap-tools

2018-08-22 Thread Ben Hutchings
On Mon, 2018-08-20 at 11:04 +0200, Ricardo Ribalda Delgado wrote: > Hello Ming > On Mon, Aug 20, 2018 at 10:30 AM Ming Lei wrote: [...] > > One problem found from your iostat log is that looks there is ~30sec > > idle period between IO activities when blk-mq is enabled. > > During all the test th

Re: [PATCH] blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait

2018-08-22 Thread Jens Axboe
On 8/22/18 1:12 PM, Holger Hoffstätte wrote: > On 08/22/18 19:28, Jens Axboe wrote: >> On 8/22/18 8:27 AM, Jens Axboe wrote: >>> On 8/22/18 6:54 AM, Holger Hoffstätte wrote: On 08/22/18 06:10, Jens Axboe wrote: > [...] > If you have time, please look at the 3 patches I posted earlier t

Re: [PATCH] blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait

2018-08-22 Thread Holger Hoffstätte
On 08/22/18 19:28, Jens Axboe wrote: On 8/22/18 8:27 AM, Jens Axboe wrote: On 8/22/18 6:54 AM, Holger Hoffstätte wrote: On 08/22/18 06:10, Jens Axboe wrote: [...] If you have time, please look at the 3 patches I posted earlier today. Those are for mainline, so should be OK :-) I'm just playi

Re: [PATCH v2] bcache: release dc->writeback_lock properly in bch_writeback_thread()

2018-08-22 Thread Jens Axboe
On 8/22/18 12:07 PM, Coly Li wrote: > On 2018/8/23 2:02 AM, Coly Li wrote: >> From: Shan Hai >> >> The writeback thread would exit with a lock held when the cache device is >> detached via sysfs interface, fix it by releasing the held lock before >> exiting >> the while-loop. >> >> Fixes: fadd94e

Re: [PATCH v2] bcache: release dc->writeback_lock properly in bch_writeback_thread()

2018-08-22 Thread Coly Li
On 2018/8/23 2:02 AM, Coly Li wrote: > From: Shan Hai > > The writeback thread would exit with a lock held when the cache device is > detached via sysfs interface, fix it by releasing the held lock before exiting > the while-loop. > > Fixes: fadd94e05c02 (bcache: quit dc->writeback_thread when

[PATCH v2] bcache: release dc->writeback_lock properly in bch_writeback_thread()

2018-08-22 Thread Coly Li
From: Shan Hai The writeback thread would exit with a lock held when the cache device is detached via sysfs interface, fix it by releasing the held lock before exiting the while-loop. Fixes: fadd94e05c02 (bcache: quit dc->writeback_thread when BCACHE_DEV_DETACHING is set) Signed-off-by: Shan Ha

[GIT PULL] Follow up block changes for this merge window

2018-08-22 Thread Jens Axboe
) - blk-mq hardware queue count update fix (Jianchao) - Various little fixes Please pull! git://git.kernel.dk/linux-block.git tags/for-4.19/post-20180822 Chaitanya Kulkarni (1): block: remove duplicate initialization

[PATCH] bcache: release dc->writeback_lock properly in bch_writeback_thread()

2018-08-22 Thread Coly Li
From: Shan Hai The writeback thread would exit with a lock held when the cache device is detached via sysfs interface, fix it by releasing the held lock before exiting the while-loop. Signed-off-by: Shan Hai Signed-off-by: Coly Li Tested-by: Shenghui Wang Cc: sta...@vger.kernel.org #4.17+ ---

Re: [PATCH] block: don't warn when calling fsync on read-only block devices

2018-08-22 Thread Jens Axboe
On 8/22/18 10:23 AM, Mikulas Patocka wrote: > It is possible to call fsync on a read-only handle (for example, fsck.ext2 > does it when doing read-only check), and this call results in kernel > warning. This bug was introduced by the commit 721c7fc701c7 "block: fail > op_is_write() requests to r

[PATCH] block: don't warn when calling fsync on read-only block devices

2018-08-22 Thread Mikulas Patocka
It is possible to call fsync on a read-only handle (for example, fsck.ext2 does it when doing read-only check), and this call results in kernel warning. This bug was introduced by the commit 721c7fc701c7 "block: fail op_is_write() requests to read-only partitions". Signed-off-by: Mikulas Patock

Re: [PATCH v2] block: fix rdma queue mapping

2018-08-22 Thread Christoph Hellwig
On Mon, Aug 20, 2018 at 01:54:20PM -0700, Sagi Grimberg wrote: > nvme-rdma attempts to map queues based on irq vector affinity. > However, for some devices, completion vector irq affinity is > configurable by the user which can break the existing assumption > that irq vectors are optimally arranged

Re: [PATCH v5 3/3] block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

2018-08-22 Thread Jan Kara
On Wed 22-08-18 18:50:53, Ming Lei wrote: > On Wed, Aug 22, 2018 at 12:33:05PM +0200, Jan Kara wrote: > > On Wed 22-08-18 10:02:49, Martin Wilck wrote: > > > On Mon, 2018-07-30 at 20:37 +0800, Ming Lei wrote: > > > > On Wed, Jul 25, 2018 at 11:15:09PM +0200, Martin Wilck wrote: > > > > > > > > > >

Re: [PATCH v5 3/3] block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

2018-08-22 Thread Ming Lei
On Wed, Aug 22, 2018 at 12:33:05PM +0200, Jan Kara wrote: > On Wed 22-08-18 10:02:49, Martin Wilck wrote: > > On Mon, 2018-07-30 at 20:37 +0800, Ming Lei wrote: > > > On Wed, Jul 25, 2018 at 11:15:09PM +0200, Martin Wilck wrote: > > > > > > > > +/** > > > > + * bio_iov_iter_get_pages - pin user or

Re: [PATCH v5 3/3] block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

2018-08-22 Thread Jan Kara
On Wed 22-08-18 10:02:49, Martin Wilck wrote: > On Mon, 2018-07-30 at 20:37 +0800, Ming Lei wrote: > > On Wed, Jul 25, 2018 at 11:15:09PM +0200, Martin Wilck wrote: > > > > > > +/** > > > + * bio_iov_iter_get_pages - pin user or kernel pages and add them > > > to a bio > > > + * @bio: bio to add p

Re: SDHCI Regression with 6ce3dd6eec11 ("blk-mq: issue directly if hw queue isn't busy in case of 'none'")

2018-08-22 Thread Ming Lei
On Wed, Aug 22, 2018 at 09:06:40AM +0300, Jarkko Nikula wrote: > On 08/21/2018 04:57 PM, Ming Lei wrote: > > On Tue, Aug 21, 2018 at 04:45:41PM +0300, Jarkko Nikula wrote: > > > On 08/21/2018 04:03 PM, Adrian Hunter wrote: > > > > On 21/08/18 15:37, Jarkko Nikula wrote: > > > > > Hi > > > > > > >

Re: [PATCH v5 3/3] block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

2018-08-22 Thread Martin Wilck
On Mon, 2018-07-30 at 20:37 +0800, Ming Lei wrote: > On Wed, Jul 25, 2018 at 11:15:09PM +0200, Martin Wilck wrote: > > > > +/** > > + * bio_iov_iter_get_pages - pin user or kernel pages and add them > > to a bio > > + * @bio: bio to add pages to > > + * @iter: iov iterator describing the region to

Re: [PATCH 1/1] bcache: release the lock before stopping the writeback thread

2018-08-22 Thread Shan Hai
Hi Coly, On 2018年08月22日 15:29, Coly Li wrote: Hi Shan, On 2018/8/22 3:00 PM, Shan Hai wrote: The writeback thread would exit with a lock held when the cache device is detached via sysfs interface, fix it by releasing the held lock before exiting the thread. I will change "the thread" to "the

Re: [PATCH 1/1] bcache: release the lock before stopping the writeback thread

2018-08-22 Thread Coly Li
Hi Shan, On 2018/8/22 3:00 PM, Shan Hai wrote: > The writeback thread would exit with a lock held when the cache device is > detached via sysfs interface, fix it by releasing the held lock before exiting > the thread. I will change "the thread" to "the while-loop" when I apply this patch. > > S

[PATCH 1/1] bcache: release the lock before stopping the writeback thread

2018-08-22 Thread Shan Hai
The writeback thread would exit with a lock held when the cache device is detached via sysfs interface, fix it by releasing the held lock before exiting the thread. Signed-off-by: Shan Hai --- drivers/md/bcache/writeback.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/dr