[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLAPR08MB690003D5D175FC784DE844F8B81C9@BLAPR08MB6900.namprd08.prod.outlook.com>
Date: Mon, 5 Jul 2021 11:15:51 +0000
From: "Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@...ron.com>
To: Christoph Hellwig <hch@....de>
CC: "kbusch@...nel.org" <kbusch@...nel.org>,
"axboe@...com" <axboe@...com>,
"sagi@...mberg.me" <sagi@...mberg.me>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"shiva.linuxworks@...il.com" <shiva.linuxworks@...il.com>
Subject: RE: [EXT] Re: [PATCH] nvme: Add abrupt shutdown support
Micron Confidential
> >
> > Hi Christoph,
> >
> > >
> > >
> > > On Mon, Jul 05, 2021 at 10:11:57AM +0000, shiva.linuxworks@...il.com
> wrote:
> > > > From: Shivamurthy Shastri <sshivamurthy@...ron.com>
> > > >
> > > > Enabling the abrupt shutdown support. In this shutdown type host does
> > > > not need to send Delete I/O Submission Queue and Delete I/O Completion
> > > > queue commands to the device.
> > >
> > > Why?
> >
> > This is to achieve faster shutdown at the cost of data in-flight.
>
> What is the actual use case, and why would a module paramter be a good
> interface?
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.
Thanks,
Shiva
Micron Confidential
Powered by blists - more mailing lists