From: stuart hayes <stuart.w.hayes@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Martin Belanger <Martin.Belanger@dell.com>,
Oliver O'Halloran <oohall@gmail.com>,
Daniel Wagner <dwagner@suse.de>, Keith Busch <kbusch@kernel.org>,
Lukas Wunner <lukas@wunner.de>,
David Jeffery <djeffery@redhat.com>,
Jeremy Allison <jallison@ciq.com>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v7 3/4] driver core: shut down devices asynchronously
Date: Tue, 2 Jul 2024 14:00:05 -0500 [thread overview]
Message-ID: <13d0a0db-e113-42c4-9fbe-74ebfa46f46b@gmail.com> (raw)
In-Reply-To: <20240702050414.GA22160@lst.de>
On 7/2/2024 12:04 AM, Christoph Hellwig wrote:
> On Mon, Jul 01, 2024 at 12:57:40PM -0500, stuart hayes wrote:
>>> We discussed this before, but there is no summary of it and I of course
>>> forgot the conclusion:
>>>
>>> - why don't we do this by default?
>>
>> It is done by default in this version, for devices whose drivers opt-in.
>>
>> In the previous discussion, you mentioned that you thought "safe" was the
>> only sensible option (where "safe" was driver opt-in to async shutdown)...
>> that is the default (and only) option with this version. Greg K-H also
>> requested opt-in as well, and suggested that "on" (driver opt-out) could
>> be removed.
>>
>>> - why is it safe to user enable it?
>>
>> I guess it isn't necessarily safe, if there are any drivers that can't
>> handle their devices shutting down asynchronously. I thought it would be
>> nice to be able to enable driver opt-in from user space for testing, before
>> changing the default setting for the driver.
>
> I was mostly getting into the contradiction that either we think the
> async shutdown is safe everywhere, in which case we don't need a driver
> opt-in, or it is not, in which case allowing user to just enabled it
> also seems like a bad idea.
>
I understand. My thinking was that is was very likely to be safe (the initial
version of this patch didn't have an opt-in or opt-out).
I have no issue removing the sysfs attribute if you think that's best.
>> I can correct these lines. I thought that an 80 character line length limit
>> was no longer required, and saw another line a few lines above these that was
>> even longer... and the checkpatch script didn't flag it either.
>
> checkpatch is unfortunately completely broken, it flags totally harmless
> things and doesn't catch other things. > 80 characters are allowed for
> individual lines where it improves readability. The exact definition
> of that depends on the maintainers and reviewers, but outside of
> string constants I can't really find anything where it does.
Got it, thanks for the feedback.
next prev parent reply other threads:[~2024-07-02 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 19:46 [PATCH v7 0/4] shut down devices asynchronously Stuart Hayes
2024-06-26 19:46 ` [PATCH v7 1/4] driver core: don't always lock parent in shutdown Stuart Hayes
2024-06-27 5:51 ` Christoph Hellwig
2024-06-27 7:30 ` Greg Kroah-Hartman
2024-06-26 19:46 ` [PATCH v7 2/4] driver core: separate function to shutdown one device Stuart Hayes
2024-06-27 5:51 ` Christoph Hellwig
2024-06-26 19:46 ` [PATCH v7 3/4] driver core: shut down devices asynchronously Stuart Hayes
2024-06-27 5:55 ` Christoph Hellwig
2024-07-01 17:57 ` stuart hayes
2024-07-02 5:04 ` Christoph Hellwig
2024-07-02 19:00 ` stuart hayes [this message]
2024-06-26 19:46 ` [PATCH v7 4/4] nvme-pci: Make driver prefer asynchronous shutdown Stuart Hayes
2024-06-26 19:58 ` [PATCH v7 0/4] shut down devices asynchronously Keith Busch
2024-06-30 8:49 ` Sagi Grimberg
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=13d0a0db-e113-42c4-9fbe-74ebfa46f46b@gmail.com \
--to=stuart.w.hayes@gmail.com \
--cc=Martin.Belanger@dell.com \
--cc=axboe@fb.com \
--cc=djeffery@redhat.com \
--cc=dwagner@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jallison@ciq.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lukas@wunner.de \
--cc=oohall@gmail.com \
--cc=rafael@kernel.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 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.