From: keith.busch@intel.com (Keith Busch)
Subject: Problems writing to intel P3700 NVMe drive
Date: Thu, 28 May 2015 21:31:00 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1505282123410.15930@localhost.lm.intel.com> (raw)
In-Reply-To: <CAFMq3wGafXvcB0jO4myzYA83trOfCyoo8rNVTNa1qTD7okytDQ@mail.gmail.com>
Using 'pcie_bus_perf' will work just fine in most cases, selecting the
highest capable settings so as not to penalize other h/w. Though all
your controllers had the same max payload capabilities anyway, so they
should all be the same from the max TLP perspective.
On Thu, 28 May 2015, Pavilion Storage wrote:
> The root cause might be a bug in the kernel where pcie devices are
> configured. Setting it to 128B will work, but may not perform to the
> best capabilities allowed by the device and RC. If we have multiple
> drives from different manufacturers in the system, we may penalize the
> drive that has the hardware capability to handle higher MPSS.
>
> thx
> Kishore
>
>
> On Thu, May 28, 2015@2:03 PM, Keith Busch <keith.busch@intel.com> wrote:
>> Perhaps not a desirable/permanent solution, but for everyone's benefit,
>> we can work-around the problem with kernel parameter:
>>
>> pci=pcie_bus_safe
>>
>> Using 'pcie_bus_perf' instead may also work, though your original
>> solution of just using x86 sounded perfectly reasonable to me. :)
>>
>> On Thu, 28 May 2015, Pavilion Storage wrote:
>>>
>>> Thanks to Keith Busch for the providing the clues.
>>> The problem was that the PCIe MPSS on the drive and the CPU root
>>> complex did not match and that caused a problem. Setting it to a
>>> common value fixed the problem.
>>> Kishore
>
next prev parent reply other threads:[~2015-05-28 21:31 UTC|newest]
Thread overview: 15+ 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 [this message]
2015-06-03 20:10 ` Keith Busch
2015-06-03 20:20 ` Bjorn Helgaas
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.1505282123410.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox