Re: Testing latest linux-next 4.9 ib_srp and ib_srpt
From: Laurence Oberman <hidden>
Date: 2016-12-22 02:10:17
Also in:
linux-scsi
Subsystem:
filesystems (vfs and infrastructure), the rest · Maintainers:
Alexander Viro, Christian Brauner, Linus Torvalds
Possibly related (same subject, not in this thread)
- 2016-12-22 · Re: Testing latest linux-next 4.9 ib_srp and ib_srpt · Christoph Hellwig <hidden>
- 2016-12-21 · Re: Testing latest linux-next 4.9 ib_srp and ib_srpt · Bart Van Assche <hidden>
- 2016-12-21 · Re: Testing latest linux-next 4.9 ib_srp and ib_srpt · Laurence Oberman <hidden>
- 2016-12-21 · Re: Testing latest linux-next 4.9 ib_srp and ib_srpt · Laurence Oberman <hidden>
- 2016-12-20 · Re: Testing latest linux-next 4.9 ib_srp and ib_srpt · Laurence Oberman <hidden>
----- Original Message -----
From: "Laurence Oberman" <redacted> To: "Bart Van Assche" <redacted> Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Sent: Wednesday, December 21, 2016 1:34:01 AM Subject: Re: Testing latest linux-next 4.9 ib_srp and ib_srpt ----- Original Message -----quoted
From: "Laurence Oberman" <redacted> To: "Bart Van Assche" <redacted> Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Sent: Tuesday, December 20, 2016 10:31:34 PM Subject: Re: Testing latest linux-next 4.9 ib_srp and ib_srpt ----- Original Message -----quoted
From: "Laurence Oberman" <redacted> To: "Bart Van Assche" <redacted> Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Sent: Tuesday, December 20, 2016 3:44:42 PM Subject: Re: Testing latest linux-next 4.9 ib_srp and ib_srpt ----- Original Message -----quoted
From: "Laurence Oberman" <redacted> To: "Bart Van Assche" <redacted> Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Sent: Tuesday, December 20, 2016 2:43:48 PM Subject: Re: Testing latest linux-next 4.9 ib_srp and ib_srpt ----- Original Message -----quoted
From: "Laurence Oberman" <redacted> To: "Bart Van Assche" <redacted> Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Sent: Tuesday, December 20, 2016 2:33:26 PM Subject: Re: Testing latest linux-next 4.9 ib_srp and ib_srpt Hello Bart I pulled the latest linux-next and built kernels for both server and client to rerun all my EDR tests for srp. For some reason the I/O size is being capped again to 1MB in my testing. Using my same testbed. Remember we spent a lot of time making sure we could do 4MB I/O :) Its working fine in the RHEL 7.3 kernel so before I start going back testing upstream kernels decided to ask. Have you tested large I/O with latest linux-next Server Configuration --------------------- Linux fedstorage.bos.redhat.com 4.9.0+ [root@fedstorage modprobe.d]# cat ib_srp.conf options ib_srp cmd_sg_entries=64 indirect_sg_entries=2048 [root@fedstorage modprobe.d]# cat ib_srpt.conf options ib_srpt srp_max_req_size=8296 Also Using # Set the srp_sq_size for i in /sys/kernel/config/target/srpt/0xfe800000000000007cfe900300726e4e /sys/kernel/config/target/srpt/0xfe800000000000007cfe900300726e4f do echo 16384 > $i/tpgt_1/attrib/srp_sq_size done Client Configuration -------------------- Linux ibclient 4.9.0+ [root@ibclient modprobe.d]# cat ib_srp.conf options ib_srp cmd_sg_entries=255 indirect_sg_entries=2048 dd if=/dev/sdw bs=4096k of=/dev/null iflag=direct ### RECORD 4 >>> ibclient <<< (1482261733.001) (Tue Dec 20 14:22:13 2016) ### # DISK STATISTICS (/sec) # <---------reads---------------><---------writes--------------><--------averages--------> Pct #Time Name KBytes Merged IOs Size Wait KBytes Merged IOs Size Wait RWSize QLen Wait SvcTim Util 14:22:13 sdw 1373184 0 1341 1024 2 0 0 0 0 0 1024 3 2 0 97 If I reboot into my 7.3 kernel its back to what I expect dd if=/dev/sdw bs=4096k of=/dev/null iflag=direct ### RECORD 3 >>> ibclient <<< (1482262254.001) (Tue Dec 20 14:30:54 2016) ### # DISK STATISTICS (/sec) # <---------reads---------------><---------writes--------------><--------averages--------> Pct #Time Name KBytes Merged IOs Size Wait KBytes Merged IOs Size Wait RWSize QLen Wait SvcTim Util 14:30:54 sdw 172032 129 42 4096 3 0 0 0 0 0 4096 1 3 3 130 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlHi Bart, Just FYI That dd snap was just as I had stopped the dd. Here is a stable dd snap with the RHEL kernel, I just noticed the merging, need to reboot back into upstream to compare again. No merging seen in upstream. Thanks Laurence ### RECORD 6 >>> ibclient <<< (1482262723.001) (Tue Dec 20 14:38:43 2016) ### # DISK STATISTICS (/sec) # <---------reads---------------><---------writes--------------><--------averages--------> Pct #Time Name KBytes Merged IOs Size Wait KBytes Merged IOs Size Wait RWSize QLen Wait SvcTim Util 14:38:43 sdw 1200128 879 293 4096 3 0 0 0 0 0 4096 1 3 3 95 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReplying to my own message to keep the thread going This is Linux ibclient 4.8.0-rc4 Behaves like I expected, and I see the 4MB I/O sizes. as I had already tested this. dd if=/dev/sdw bs=4096k of=/dev/null iflag=direct ### RECORD 6 >>> ibclient <<< (1482266543.001) (Tue Dec 20 15:42:23 2016) ### # DISK STATISTICS (/sec) # <---------reads---------------><---------writes--------------><--------averages--------> Pct #Time Name KBytes Merged IOs Size Wait KBytes Merged IOs Size Wait RWSize QLen Wait SvcTim Util 15:42:23 sdw 278528 201 68 4096 2 0 0 0 0 0 4096 1 2 2 206 Rebooting back into 4.9 and will bisect leading to it once I confirm -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlSo this is where I got to here: These all worked and I get the 4MB I/O size with direct I/O v4.8-rc4 v4.8-rc5 v4.8-rc6 v4.8-rc7 v4.8-rc8 v4.9 v4.9-rc1 v4.9-rc2 v4.9-rc3 v4.9-rc4 v4.9-rc5 v4.9-rc6 v4.9-rc7 v4.9-rc8 Then git checkout master and build final test kernel 4.9.0+ This one fails # DISK STATISTICS (/sec) # <---------reads---------------><---------writes--------------><--------averages--------> Pct #Time Name KBytes Merged IOs Size Wait KBytes Merged IOs Size Wait RWSize QLen Wait SvcTim Util 22:12:48 sdw 1413120 0 1380 1024 2 0 0 0 0 0 1024 3 2 0 99 22:12:49 sdw 1409024 0 1376 1024 2 0 0 0 0 0 1024 3 2 0 98 22:12:50 sdw 1445888 0 1412 1024 2 0 0 0 0 0 1024 3 2 0 98 22:12:51 sdw 1429504 0 1396 1024 2 0 0 0 0 0 1024 3 2 0 98 22:12:52 sdw 1426432 0 1393 1024 2 0 0 0 0 0 1024 3 2 0 98 22:12:53 sdw 1408000 0 1375 1024 2 0 0 0 0 0 1024 3 2 0 98 *** **** **** The last commit for 4.9-rc8 was 3e5de27 Between this and the master checkout HEAD there are 2313 lines of commits This was the giant merge. Something broke here. I guess I will have to bisect the hard way, unless somebody realizes which of the commits broke it. Commits for SRP, none of these look like candidates to break the I/O size and merge 9032ad7 Merge branches 'misc', 'qedr', 'reject-helpers', 'rxe' and 'srp' into merge-test 4fa354c IB/srp: Make writing the add_target sysfs attr interruptible 290081b IB/srp: Make mapping failures easier to debug 3787d99 IB/srp: Make login failures easier to debug 042dd76 IB/srp: Introduce a local variable in srp_add_one() 1a1faf7 IB/srp: Fix CONFIG_DYNAMIC_DEBUG=n build 0d38c24 IB/srpt: Report login failures only once dm related, however I am testing against an sd, not dm device here ef548c5 dm flakey: introduce "error_writes" feature e99dda8f dm cache policy smq: use hash_32() instead of hash_32_generic() 027c431 dm crypt: reject key strings containing whitespace chars b446396 dm space map: always set ev if sm_ll_mutate() succeeds 0c79ce0 dm space map metadata: skip useless memcpy in metadata_ll_init_index() 314c25c dm space map metadata: fix 'struct sm_metadata' leak on failed create 58fc4fe Documentation: dm raid: define data_offset status field 11e2968 dm raid: fix discard support regression affa9d2 dm raid: don't allow "write behind" with raid4/5/6 54cd640 dm mpath: use hw_handler_params if attached hw_handler is same as requested c538f6e dm crypt: add ability to use keys from the kernel key retention service 0637018 dm array: remove a dead assignment in populate_ablock_with_values() 6080758 dm ioctl: use offsetof() instead of open-coding it b23df0d dm rq: simplify use_blk_mq initialization 41c73a4 dm bufio: drop the lock when doing GFP_NOIO allocation d12067f dm bufio: don't take the lock in dm_bufio_shrink_count 9ea61ca dm bufio: avoid sleeping while holding the dm_bufio lock 5b8c01f dm table: simplify dm_table_determine_type() 301fc3f dm table: an 'all_blk_mq' table must be loaded for a blk-mq DM device 6936c12 dm table: fix 'all_blk_mq' inconsistency when an empty table is loaded I have time next week so will try narrow it down via bisect by commit Thanks Laurence -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlStarted with bisect at > 6000 revisions and 13 cycles between v4.9-rc8 and master. bisect good for v4.9-rc8, bisect bad for master HEAD Down to around 700 now, but its late, going to bed now so will finish tomorrow Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Bart, Christoph
After multiple bisects (6000 revisions, 13 cycles), I got to this one.
Of course there are a huge amount of block layer changes as we know in rc10.
[loberman@ibclient linux-next.orig]$ git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[542ff7bf18c63cf403e36a4a1c71d86dc120d924] block: new direct I/O implementation
This commit is the one that seems to have changed the behavior.
Max I/O size restricted 1MB, even when 4MB I/O is requested, no merging seen.
This is not going to only affect SRP targets.
I will review the code and will be happy to test any patches.
I will leave the test bed in place.
commit 542ff7bf18c63cf403e36a4a1c71d86dc120d924
Author: Christoph Hellwig [off-list ref]
Date: Wed Nov 16 23:14:22 2016 -0700
block: new direct I/O implementation
Similar to the simple fast path, but we now need a dio structure to
track multiple-bio completions. It's basically a cut-down version
of the new iomap-based direct I/O code for filesystems, but without
all the logic to call into the filesystem for extent lookup or
allocation, and without the complex I/O completion workqueue handler
for AIO - instead we just use the FUA bit on the bios to ensure
data is flushed to stable storage.
Signed-off-by: Christoph Hellwig [off-list ref]
Signed-off-by: Jens Axboe [off-list ref]
diff --git a/fs/block_dev.c b/fs/block_dev.c
index a1b9abe..35cc494 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c@@ -270,11 +270,161 @@ static void blkdev_bio_end_io_simple(struct bio *bio) return ret; } +struct blkdev_dio { + union { + struct kiocb *iocb; + struct task_struct *waiter; + }; + size_t size; + atomic_t ref; + bool multi_bio : 1; + bool should_dirty : 1; + bool is_sync : 1; + struct bio bio; +}; + +static struct bio_set *blkdev_dio_pool __read_mostly; + +static void blkdev_bio_end_io(struct bio *bio) +{ + struct blkdev_dio *dio = bio->bi_private; + bool should_dirty = dio->should_dirty; + + if (dio->multi_bio && !atomic_dec_and_test(&dio->ref)) { + if (bio->bi_error && !dio->bio.bi_error) + dio->bio.bi_error = bio->bi_error; + } else { + if (!dio->is_sync) { + struct kiocb *iocb = dio->iocb; + ssize_t ret = dio->bio.bi_error; + + if (likely(!ret)) { + ret = dio->size; + iocb->ki_pos += ret; + } + + dio->iocb->ki_complete(iocb, ret, 0); + bio_put(&dio->bio); + } else { + struct task_struct *waiter = dio->waiter; + + WRITE_ONCE(dio->waiter, NULL); + wake_up_process(waiter); + } + } + + if (should_dirty) { + bio_check_pages_dirty(bio); + } else { + struct bio_vec *bvec; + int i; + + bio_for_each_segment_all(bvec, bio, i) + put_page(bvec->bv_page); + bio_put(bio); + } +} + static ssize_t -blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter) +__blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages) { struct file *file = iocb->ki_filp; struct inode *inode = bdev_file_inode(file); + struct block_device *bdev = I_BDEV(inode); + unsigned blkbits = blksize_bits(bdev_logical_block_size(bdev)); + struct blkdev_dio *dio; + struct bio *bio; + bool is_read = (iov_iter_rw(iter) == READ); + loff_t pos = iocb->ki_pos; + blk_qc_t qc = BLK_QC_T_NONE; + int ret; + + if ((pos | iov_iter_alignment(iter)) & ((1 << blkbits) - 1)) + return -EINVAL; + + bio = bio_alloc_bioset(GFP_KERNEL, nr_pages, blkdev_dio_pool); + bio_get(bio); /* extra ref for the completion handler */ + + dio = container_of(bio, struct blkdev_dio, bio); + dio->is_sync = is_sync_kiocb(iocb); + if (dio->is_sync) + dio->waiter = current; + else + dio->iocb = iocb; + + dio->size = 0; + dio->multi_bio = false; + dio->should_dirty = is_read && (iter->type == ITER_IOVEC); + + for (;;) { + bio->bi_bdev = bdev; + bio->bi_iter.bi_sector = pos >> blkbits; + bio->bi_private = dio; + bio->bi_end_io = blkdev_bio_end_io; + + ret = bio_iov_iter_get_pages(bio, iter); + if (unlikely(ret)) { + bio->bi_error = ret; + bio_endio(bio); + break; + } + + if (is_read) { + bio->bi_opf = REQ_OP_READ; + if (dio->should_dirty) + bio_set_pages_dirty(bio); + } else { + bio->bi_opf = dio_bio_write_op(iocb); + task_io_account_write(bio->bi_iter.bi_size); + } + + dio->size += bio->bi_iter.bi_size; + pos += bio->bi_iter.bi_size; + + nr_pages = iov_iter_npages(iter, BIO_MAX_PAGES); + if (!nr_pages) { + qc = submit_bio(bio); + break; + } + + if (!dio->multi_bio) { + dio->multi_bio = true; + atomic_set(&dio->ref, 2); + } else { + atomic_inc(&dio->ref); + } + + submit_bio(bio); + bio = bio_alloc(GFP_KERNEL, nr_pages); + } + + if (!dio->is_sync) + return -EIOCBQUEUED; + + for (;;) { + set_current_state(TASK_UNINTERRUPTIBLE); + if (!READ_ONCE(dio->waiter)) + break; + + if (!(iocb->ki_flags & IOCB_HIPRI) || + !blk_mq_poll(bdev_get_queue(bdev), qc)) + io_schedule(); + } + __set_current_state(TASK_RUNNING); + + ret = dio->bio.bi_error; + if (likely(!ret)) { + ret = dio->size; + iocb->ki_pos += ret; + } + + bio_put(&dio->bio); + return ret; +} + +static ssize_t +blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter) +{ int nr_pages; nr_pages = iov_iter_npages(iter, BIO_MAX_PAGES + 1);
@@ -282,10 +432,18 @@ static void blkdev_bio_end_io_simple(struct bio *bio) return 0; if (is_sync_kiocb(iocb) && nr_pages <= BIO_MAX_PAGES) return __blkdev_direct_IO_simple(iocb, iter, nr_pages); - return __blockdev_direct_IO(iocb, inode, I_BDEV(inode), iter, - blkdev_get_block, NULL, NULL, - DIO_SKIP_DIO_COUNT); + + return __blkdev_direct_IO(iocb, iter, min(nr_pages, BIO_MAX_PAGES)); +} + +static __init int blkdev_init(void) +{ + blkdev_dio_pool = bioset_create(4, offsetof(struct blkdev_dio, bio)); + if (!blkdev_dio_pool) + return -ENOMEM; + return 0; } +module_init(blkdev_init); int __sync_blockdev(struct block_device *bdev, int wait) {
Thanks Laurence -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html