From: Tokunori Ikegami <ikegami.t@gmail.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] block, nvme: Increase max segments parameter setting value
Date: Tue, 24 Mar 2020 08:09:19 +0900 [thread overview]
Message-ID: <cff52955-e55c-068a-44a6-8ed4edc0696f@gmail.com> (raw)
In-Reply-To: <BYAPR04MB4965BAF4C0300E1206B049A586F00@BYAPR04MB4965.namprd04.prod.outlook.com>
Hi,
> The change looks okay, but why do we need such a large data length ?
>
> Do you have a use-case or performance numbers ?
We use the large data length to get log page by the NVMe admin command.
In the past it was able to get with the same length but failed currently
with it.
So it seems that depended on the kernel version as caused by the version up.
Also I have confirmed that currently failed with the length 0x10000000
256MB.
Regards,
Ikegami
next prev parent reply other threads:[~2020-03-23 23:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 18:23 [PATCH] block, nvme: Increase max segments parameter setting value Tokunori Ikegami
2020-03-23 19:14 ` Chaitanya Kulkarni
2020-03-23 23:09 ` Tokunori Ikegami [this message]
2020-03-24 0:02 ` Keith Busch
2020-03-24 16:51 ` Tokunori Ikegami
2020-03-27 17:50 ` Tokunori Ikegami
2020-03-27 18:18 ` Keith Busch
2020-03-28 2:11 ` Ming Lei
2020-03-28 3:13 ` Keith Busch
2020-03-28 8:28 ` Ming Lei
2020-03-28 12:57 ` Tokunori Ikegami
2020-03-29 3:01 ` Ming Lei
2020-03-30 9:15 ` Tokunori Ikegami
2020-03-30 13:53 ` Keith Busch
2020-03-31 15:24 ` Tokunori Ikegami
2020-03-31 14:13 ` Joshi
2020-03-31 15:37 ` Tokunori Ikegami
2020-03-24 7:16 ` Hannes Reinecke
2020-03-24 17:17 ` Tokunori Ikegami
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cff52955-e55c-068a-44a6-8ed4edc0696f@gmail.com \
--to=ikegami.t@gmail.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).