diff for duplicates of <20180118175316.GA11338@chelsio.com> diff --git a/a/1.txt b/N1/1.txt index 2335d0b..3e07448 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -46,7 +46,7 @@ On Thursday, January 01/18/18, 2018 at 15:28:42 +0530, Nicholas A. Bellinger wro > > Its seen with block size >= 2M on a single target 1 RAM disk config. And similar to Michals report; > > rather quickly, in a matter of seconds. > > -> > fio --rw=read --bs=2048k --numjobs=1 --iodepth=128 --runtime=30 --size=20g --loops=1 --ioengine=libaio +> > fio --rw=read --bs 48k --numjobs=1 --iodepth\x128 --runtime0 --size g --loops=1 --ioengine=libaio > > --direct=1 --invalidate=1 --fsync_on_close=1 --norandommap --exitall --filename=/dev/sdb --name=sdb > > > @@ -65,7 +65,7 @@ Yes they are IO size specific, I observed SQ overflow with fio for IO sizes abov > originally utilized by qla2xxx here: > > target/qla2xxx: Honor max_data_sg_nents I/O transfer limit -> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f9b565482c537821588444e09ff732c7d65ed6e +> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id¸9b565482c537821588444e09ff732c7d65ed6e > > Note this patch also will return a smaller Block Limits VPD (0x86) > MAXIMUM TRANSFER LENGTH based on max_data_sg_nents * PAGE_SIZE, which @@ -108,4 +108,8 @@ With above change, SQ overflow isn't observed. I started of with max_data_sg_nen > > That said, Sagi, any further comments as what else iser-target should be > doing to avoid repeated queue-fulls with limited hw sges..? -> +> +-- +To unsubscribe from this list: send the line "unsubscribe target-devel" in +the body of a message to majordomo@vger.kernel.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 65c79fb..55c8002 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,7 +10,7 @@ "ref\01516269522.24576.274.camel@haakon3.daterainc.com\0" "From\0Potnuri Bharat Teja <bharat@chelsio.com>\0" "Subject\0Re: SQ overflow seen running isert traffic with high block sizes\0" - "Date\0Thu, 18 Jan 2018 23:23:17 +0530\0" + "Date\0Thu, 18 Jan 2018 17:53:47 +0000\0" "To\0Nicholas A. Bellinger <nab@linux-iscsi.org>\0" "Cc\0Shiraz Saleem <shiraz.saleem@intel.com>" Kalderon @@ -72,7 +72,7 @@ "> > Its seen with block size >= 2M on a single target 1 RAM disk config. And similar to Michals report;\n" "> > rather quickly, in a matter of seconds.\n" "> > \n" - "> > fio --rw=read --bs=2048k --numjobs=1 --iodepth=128 --runtime=30 --size=20g --loops=1 --ioengine=libaio \n" + "> > fio --rw=read --bs 48k --numjobs=1 --iodepth\0228 --runtime0 --size g --loops=1 --ioengine=libaio \n" "> > --direct=1 --invalidate=1 --fsync_on_close=1 --norandommap --exitall --filename=/dev/sdb --name=sdb \n" "> > \n" "> \n" @@ -91,7 +91,7 @@ "> originally utilized by qla2xxx here:\n" "> \n" "> target/qla2xxx: Honor max_data_sg_nents I/O transfer limit\n" - "> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f9b565482c537821588444e09ff732c7d65ed6e\n" + "> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id\302\2709b565482c537821588444e09ff732c7d65ed6e\n" "> \n" "> Note this patch also will return a smaller Block Limits VPD (0x86)\n" "> MAXIMUM TRANSFER LENGTH based on max_data_sg_nents * PAGE_SIZE, which\n" @@ -134,6 +134,10 @@ "> \n" "> That said, Sagi, any further comments as what else iser-target should be\n" "> doing to avoid repeated queue-fulls with limited hw sges..?\n" - > + "> \n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe target-devel\" in\n" + "the body of a message to majordomo@vger.kernel.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -7664f9d2b1245c42b8ca4b574729a6ecfe5f80a539b864bd8afe6b318cb1533b +7439eecb830e03f165dd1e84d02c39a12c70c275facc7c858c418a10f9d430bf
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.