From: keith.busch@intel.com (Keith Busch)
Subject: nvme, allocation failures, and aborted commands
Date: Thu, 9 Mar 2017 18:03:34 -0500 [thread overview]
Message-ID: <20170309230334.GE14329@localhost.localdomain> (raw)
In-Reply-To: <3290252.oG8R0O7IFj@natasha>
On Thu, Mar 09, 2017@03:01:27PM -0700, Thomas Fjellstrom wrote:
> On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote:
> >
> > echo 128 > /sys/block/nvme0n1/queue/max_hw_sectors_kb
> > echo 128 > /sys/block/nvme0n1/queue/max_nr_requests
> >
>
> First off, theres no max_nr_requests, and echoing into max_hw_sectors_kb gets
> me a permission denied even as root no matter the value I tried.
What I meant to say was "max_sectors_kb" and "nr_request".
WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: Thomas Fjellstrom <thomas@fjellstrom.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: nvme, allocation failures, and aborted commands
Date: Thu, 9 Mar 2017 18:03:34 -0500 [thread overview]
Message-ID: <20170309230334.GE14329@localhost.localdomain> (raw)
In-Reply-To: <3290252.oG8R0O7IFj@natasha>
On Thu, Mar 09, 2017 at 03:01:27PM -0700, Thomas Fjellstrom wrote:
> On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote:
> >
> > echo 128 > /sys/block/nvme0n1/queue/max_hw_sectors_kb
> > echo 128 > /sys/block/nvme0n1/queue/max_nr_requests
> >
>
> First off, theres no max_nr_requests, and echoing into max_hw_sectors_kb gets
> me a permission denied even as root no matter the value I tried.
What I meant to say was "max_sectors_kb" and "nr_request".
next prev parent reply other threads:[~2017-03-09 23:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 15:27 nvme, allocation failures, and aborted commands Thomas Fjellstrom
2017-03-06 2:57 ` Thomas Fjellstrom
2017-03-06 6:11 ` Thomas Fjellstrom
2017-03-06 6:11 ` Thomas Fjellstrom
2017-03-06 22:46 ` Keith Busch
2017-03-06 22:46 ` Keith Busch
2017-03-09 22:01 ` Thomas Fjellstrom
2017-03-09 22:01 ` Thomas Fjellstrom
2017-03-09 23:03 ` Keith Busch [this message]
2017-03-09 23:03 ` Keith Busch
2017-03-11 16:31 ` Thomas Fjellstrom
2017-03-11 16:31 ` Thomas Fjellstrom
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=20170309230334.GE14329@localhost.localdomain \
--to=keith.busch@intel.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 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.