linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Mario.Limonciello@dell.com
Cc: Andrew Lutomirski <luto@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	linux-nvme <linux-nvme@lists.infradead.org>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Keith Busch <keith.busch@intel.com>
Subject: Re: [PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe
Date: Thu, 18 May 2017 18:37:41 -0700	[thread overview]
Message-ID: <CALCETrVJtYbsbJQWuEzxFpH_QFisFrJFC-X9MOKmyoiF-YuXhQ@mail.gmail.com> (raw)
In-Reply-To: <1495157575349.14067@Dell.com>

On Thu, May 18, 2017 at 6:32 PM,  <Mario.Limonciello@dell.com> wrote:
>> I pondered this a bit, and I want to NAK my own patch.  This patch
>> stinks -- there's mounting evidence that what it really does is to
>> make any problems show up more rarely.  If a system is broken, I want
>> it to be obviously broken.
>>
>> Here are two options to move forward:
>>
>> a) Leave the Dell quirk in place until someone from Dell or Samsung
>> figures out what's actually going on.  Add a blanket quirk turning off
>> the deepest sleep state on all Intel devices [1] at least until
>> someone from Intel figures out what's going on -- Hi, Keith!  Deal
>> with any other problems as they're reported.
>>
>> b) Turn off the deepest state across the board and add a whitelist.
>> Populate the whitelist a bit.  The problem is that I don't even know
>> what to whitelist.  My system works great, but does that mean that my
>> particular laptop is fine?  My particular disk is certainly *not* fine
>> when installed in other laptops.
>>
>> Ideas?  (a) is a bit simpler to implement, I think, and may be good enough.
>>
> Until we have a proper solution for XPS 9550/Precision 5510 I agree that quirk should stay in place.
> Of those two options I think A is better.  There are lots of machines this patch has helped that haven't been mentioned in this content.  Please make sure that it's not too aggressive on ITPT for PS4 if you're not aligning to RST behavior (should at "least" be 6s).

I can get on board for 6s minimum for the deepest state.  I don't want
to touch any rule that says "PS4" in the description because PS4 isn't
even guaranteed to be a sleep state, let alone the deepest state.

>
> Kai-Heng and the Canonical team have also been looking at a lot of SSD/machine combinations with these various patches.  I hope they can speak up on what they've been finding.
>
>> [1] There are problems on Intel NUC machines with Intel SSDs, for
>> crying out loud.  I realize that the team that designs the NUC is
>> probably totally unrelated to the SSD team, but they're both Intel and
>> it shouldn't be *that* hard for someone at Intel to get it debugged.
>> See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686592
>
> I would second this and love if Intel could speak up here on what direction they recommend to bring the NVME driver for APST.

  reply	other threads:[~2017-05-19  1:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12  4:06 [PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe Andy Lutomirski
2017-05-12 13:58 ` Mario.Limonciello
2017-05-12 14:04   ` Andy Lutomirski
2017-05-12 14:34     ` Mario.Limonciello
2017-05-12 23:49       ` Andy Lutomirski
2017-05-15 15:51         ` Mario.Limonciello
2017-05-13 12:27 ` Andy Lutomirski
2017-05-15 16:11   ` Mario.Limonciello
2017-05-19  1:18     ` Andy Lutomirski
2017-05-19  1:13 ` Andy Lutomirski
2017-05-19  1:32   ` Mario.Limonciello
2017-05-19  1:37     ` Andy Lutomirski [this message]
2017-05-19  6:35   ` Christoph Hellwig
2017-05-19 14:18     ` Keith Busch
2017-05-19 14:15       ` Christoph Hellwig
2017-05-19 18:24       ` Andy Lutomirski
2017-05-19 21:42         ` 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=CALCETrVJtYbsbJQWuEzxFpH_QFisFrJFC-X9MOKmyoiF-YuXhQ@mail.gmail.com \
    --to=luto@kernel.org \
    --cc=Mario.Limonciello@dell.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kai.heng.feng@canonical.com \
    --cc=keith.busch@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).