linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Jeremy Allison <jra@samba.org>, Stuart Hayes <stuart.w.hayes@gmail.com>
Cc: jallison@ciq.com, rafael@kernel.org, tansuresh@google.com,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	djeffery@redhat.com, hch@lst.de, gregkh@linuxfoundation.org,
	linux-pci@vger.kernel.org
Subject: Re: [RFC PATCH 0/6] async device shutdown support
Date: Mon, 19 Feb 2024 08:31:57 +0100	[thread overview]
Message-ID: <20240219073157.GA32010@wunner.de> (raw)
In-Reply-To: <ZcPqr+9hqH1UXdwr@jeremy-HP-Z840-Workstation>

[cc += Stuart, linux-pci; start of thread:
 https://lore.kernel.org/lkml/20240207184100.18066-1-djeffery@redhat.com/
]

On Wed, Feb 07, 2024 at 12:40:15PM -0800, Jeremy Allison wrote:
> On Wed, Feb 07, 2024 at 1:40:54PM -0500 David Jeffery wrote:
> > This is another attempt to implement an acceptable implementation of async
> > device shutdown, inspired by a previous attempt by Tanjore Suresh. For
> > systems with many disks, async shutdown can greatly reduce shutdown times
> > from having slow operations run in parallel.
> 
> It may have escaped your notice that I was shepherding a newer version
> of Tanjore's original patchset through the nvme lists already. Please
> look at version 5 here (I am working on version 6 currently).

Stuart Hayes has also been working on async shutdown and his approach
is much leaner than yours.  He needs testers.  Maybe you can give his
patch a spin and report back if it works for you, so that you guys can
collaborate instead of working on separate approaches?

Here's Stuart's v5:
https://lore.kernel.org/all/20231128210436.506510-1-stuart.w.hayes@gmail.com/

Thanks,

Lukas

  reply	other threads:[~2024-02-19  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 20:40 [RFC PATCH 0/6] async device shutdown support Jeremy Allison
2024-02-19  7:31 ` Lukas Wunner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-07 20:34 Jeremy Allison
2024-02-07 18:40 David Jeffery

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=20240219073157.GA32010@wunner.de \
    --to=lukas@wunner.de \
    --cc=djeffery@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jallison@ciq.com \
    --cc=jra@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=stuart.w.hayes@gmail.com \
    --cc=tansuresh@google.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 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).