linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Tokunori Ikegami <ikegami.t@gmail.com>
Cc: Ming Lei <tom.leiming@gmail.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH] block, nvme: Increase max segments parameter setting value
Date: Mon, 30 Mar 2020 07:53:23 -0600	[thread overview]
Message-ID: <20200330135323.GA32604@C02WT3WMHTD6> (raw)
In-Reply-To: <cc1534d1-34f6-ffdb-27bd-73590ab30437@gmail.com>

On Mon, Mar 30, 2020 at 06:15:41PM +0900, Tokunori Ikegami wrote:
> But there is a case that the command data length is limited by 512KB.
> I am not sure about this condition so needed more investigation.

Your memory is too fragmented. You need more physically contiguous
memory or you'll hit the segment limit before you hit the length
limit. Try allocating huge pages.

  reply	other threads:[~2020-03-30 13:53 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
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 [this message]
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=20200330135323.GA32604@C02WT3WMHTD6 \
    --to=kbusch@kernel.org \
    --cc=Chaitanya.Kulkarni@wdc.com \
    --cc=ikegami.t@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=tom.leiming@gmail.com \
    /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).