All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@micron.com>
Cc: Christoph Hellwig <hch@lst.de>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"shiva.linuxworks@gmail.com" <shiva.linuxworks@gmail.com>
Subject: Re: [EXT] Re: [PATCH] nvme: Add abrupt shutdown support
Date: Mon, 5 Jul 2021 13:53:49 +0200	[thread overview]
Message-ID: <20210705115349.GA20266@lst.de> (raw)
In-Reply-To: <BLAPR08MB690003D5D175FC784DE844F8B81C9@BLAPR08MB6900.namprd08.prod.outlook.com>

On Mon, Jul 05, 2021 at 11:15:51AM +0000, Shivamurthy Shastri (sshivamurthy) wrote:
> For systems with passive electronic components to handle power-loss/battery-removal,
> CC.SHN=10b will help to achieve safer shutdown with relatively lower power back-up 
> requirements (at lower cost).
> 
> The module parameter gives flexibility to the host to decide shutdown type even during
> boot failure. 

If you have a device that always prefers an abrupt please introduce a TP
in the NVMe technical working group so that the hosts automatically
do the right thing.  Requiring sysadmin intervention using a global
kernel parameter is not the way to do this.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: "Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@micron.com>
Cc: Christoph Hellwig <hch@lst.de>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"shiva.linuxworks@gmail.com" <shiva.linuxworks@gmail.com>
Subject: Re: [EXT] Re: [PATCH] nvme: Add abrupt shutdown support
Date: Mon, 5 Jul 2021 13:53:49 +0200	[thread overview]
Message-ID: <20210705115349.GA20266@lst.de> (raw)
In-Reply-To: <BLAPR08MB690003D5D175FC784DE844F8B81C9@BLAPR08MB6900.namprd08.prod.outlook.com>

On Mon, Jul 05, 2021 at 11:15:51AM +0000, Shivamurthy Shastri (sshivamurthy) wrote:
> For systems with passive electronic components to handle power-loss/battery-removal,
> CC.SHN=10b will help to achieve safer shutdown with relatively lower power back-up 
> requirements (at lower cost).
> 
> The module parameter gives flexibility to the host to decide shutdown type even during
> boot failure. 

If you have a device that always prefers an abrupt please introduce a TP
in the NVMe technical working group so that the hosts automatically
do the right thing.  Requiring sysadmin intervention using a global
kernel parameter is not the way to do this.

  reply	other threads:[~2021-07-05 11:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 10:11 [PATCH] nvme: Add abrupt shutdown support shiva.linuxworks
2021-07-05 10:11 ` shiva.linuxworks
2021-07-05 10:15 ` Christoph Hellwig
2021-07-05 10:15   ` Christoph Hellwig
2021-07-05 10:40   ` [EXT] " Shivamurthy Shastri (sshivamurthy)
2021-07-05 10:40     ` Shivamurthy Shastri (sshivamurthy)
2021-07-05 10:42     ` Christoph Hellwig
2021-07-05 10:42       ` Christoph Hellwig
2021-07-05 11:15       ` Shivamurthy Shastri (sshivamurthy)
2021-07-05 11:15         ` Shivamurthy Shastri (sshivamurthy)
2021-07-05 11:53         ` Christoph Hellwig [this message]
2021-07-05 11:53           ` Christoph Hellwig
2021-07-05 13:04           ` Keith Busch
2021-07-05 13:04             ` Keith Busch
2021-07-06  8:14             ` Shivamurthy Shastri (sshivamurthy)
2021-07-06  8:14               ` Shivamurthy Shastri (sshivamurthy)
2021-07-06 15:07               ` Keith Busch
2021-07-06 15:07                 ` 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=20210705115349.GA20266@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=shiva.linuxworks@gmail.com \
    --cc=sshivamurthy@micron.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.