From: keith.busch@intel.com (Keith Busch)
Subject: Problems writing to intel P3700 NVMe drive
Date: Wed, 3 Jun 2015 21:37:52 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1506032132350.15930@localhost.lm.intel.com> (raw)
In-Reply-To: <CAErSpo5HkLA8Yh0QeBPXL_64GaO+VcSugNHmCLR_UT+6mdM3JA@mail.gmail.com>
On Wed, 3 Jun 2015, Bjorn Helgaas wrote:
> On Wed, Jun 3, 2015@3:10 PM, Keith Busch <keith.busch@intel.com> wrote:
>> A while back, there were a few proposals on changing the pci driver's
>> default MPS tuning from the existing do-nothing policy to something
>> safe so end-users don't need to remember kernel parameters as described
>> below. Is this still active, or can we kick that back to life if not?
>
> I'd love to see some activity there. Somebody else asked me about
> this a few weeks ago, and I sent him this list of some of the things I
> think are wrong with the current situation:
Thanks for the update. I got in contact with some comrades already working
on this, so we'll post an updated proposal when it's ready. This feature
is getting more attention with broader hot plug pci-e storage usage (among
other reasons), so I'm sure we'll give this its due consideration this time.
WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Keith Busch <keith.busch@intel.com>,
Pavilion Storage <storagepavilion@gmail.com>,
linux-nvme <linux-nvme@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Problems writing to intel P3700 NVMe drive
Date: Wed, 3 Jun 2015 21:37:52 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1506032132350.15930@localhost.lm.intel.com> (raw)
In-Reply-To: <CAErSpo5HkLA8Yh0QeBPXL_64GaO+VcSugNHmCLR_UT+6mdM3JA@mail.gmail.com>
On Wed, 3 Jun 2015, Bjorn Helgaas wrote:
> On Wed, Jun 3, 2015 at 3:10 PM, Keith Busch <keith.busch@intel.com> wrote:
>> A while back, there were a few proposals on changing the pci driver's
>> default MPS tuning from the existing do-nothing policy to something
>> safe so end-users don't need to remember kernel parameters as described
>> below. Is this still active, or can we kick that back to life if not?
>
> I'd love to see some activity there. Somebody else asked me about
> this a few weeks ago, and I sent him this list of some of the things I
> think are wrong with the current situation:
Thanks for the update. I got in contact with some comrades already working
on this, so we'll post an updated proposal when it's ready. This feature
is getting more attention with broader hot plug pci-e storage usage (among
other reasons), so I'm sure we'll give this its due consideration this time.
next prev parent reply other threads:[~2015-06-03 21:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 21:30 Problems writing to intel P3700 NVMe drive Pavilion Storage
2015-05-27 22:34 ` Greg Schulz
2015-05-27 22:40 ` Pavilion Storage
2015-05-27 23:05 ` Greg Schulz
2015-05-27 23:53 ` Pavilion Storage
2015-05-28 0:24 ` j cagle
2015-05-28 0:37 ` Pavilion Storage
2015-05-28 0:46 ` Pavilion Storage
[not found] ` <CA+At7pWf6Ge3pc7=aeiqz=iWxtYJSPVdM_W2XW9pL4d22q432Q@mail.gmail.com>
[not found] ` <000a01d098ee$b52ce0c0$1f86a240$@storageio.com>
2015-05-28 20:53 ` Pavilion Storage
2015-05-28 21:03 ` Keith Busch
2015-05-28 21:19 ` Pavilion Storage
2015-05-28 21:31 ` Keith Busch
2015-06-03 20:10 ` Keith Busch
2015-06-03 20:10 ` Keith Busch
2015-06-03 20:20 ` Bjorn Helgaas
2015-06-03 20:20 ` Bjorn Helgaas
2015-06-03 21:37 ` Keith Busch [this message]
2015-06-03 21:37 ` Keith Busch
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=alpine.LNX.2.00.1506032132350.15930@localhost.lm.intel.com \
--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.