From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Enzo Matsumiya <ematsumiya@suse.de>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC PATCH] nvme: add NO APST quirk for Kioxia device
Date: Wed, 10 Nov 2021 06:08:10 +0000 [thread overview]
Message-ID: <e37edd78-a390-25a6-874b-8b69d2b80182@nvidia.com> (raw)
In-Reply-To: <20211109150405.uv2he4quk4dlud6p@cyberdelia>
Enzo,
On 11/9/2021 7:04 AM, Enzo Matsumiya wrote:
> On 11/09, Christoph Hellwig wrote:
>> On Fri, Nov 05, 2021 at 11:08:57PM -0300, Enzo Matsumiya wrote:
>>> + },
>>> + {
>>> + /*
>>> + * This Kioxia device times out and aborts I/O during any load,
>>> + * but more easily reproducible with discards (fstrim).
>>> + *
>>> + * Device is left in a state that is also not possible to
>>> use "nvme set-feature"
>>> + * to disable APST, but booting with
>>> nvme_core.default_ps_max_latency=0 works.
>>> + */
>>
>> Overly long lines here, but I can fix that up.
>
> Missed that, sorry. Thanks.
>
>> Do you have a product
>> name for this device or is just a nameless OEM controller?
>
> I didn't, had to google. I see it listed on Kioxia's website as
> CD6-V Series (6.4T model), but since customer was running on an
> DL380 Gen10, I suspect it could also be HPE PE8030 (PN P19837-B21).
>
You can get more information about this controller using nvme-cli
id-ctrl command.
>
> Cheers,
>
> Enzo
>
next prev parent reply other threads:[~2021-11-10 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 2:08 Enzo Matsumiya
2021-11-09 8:06 ` Christoph Hellwig
2021-11-09 15:04 ` Enzo Matsumiya
2021-11-10 6:08 ` Chaitanya Kulkarni [this message]
2021-11-10 15:23 ` Enzo Matsumiya
2021-11-11 10:01 ` Christoph Hellwig
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=e37edd78-a390-25a6-874b-8b69d2b80182@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@fb.com \
--cc=ematsumiya@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®