linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Allison <jallison@ciq.com>
To: linux-nvme@lists.infradead.org, Jeremy Allison <jallison@ciq.com>,
	jra@samba.org,  rafael@kernel.org,
	Tanjore Suresh <tansuresh@google.com>,
	linux-kernel@vger.kernel.org,  djeffery@redhat.com, hch@lst.de
Subject: Re: [RFC PATCH 0/6] async device shutdown support
Date: Wed, 7 Feb 2024 12:34:54 -0800	[thread overview]
Message-ID: <CADfv6Ka0M947muKa7hSuVv5Ot_tonmFNBYyrkzCQ5_KUVqN6YQ@mail.gmail.com> (raw)

> 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. The older patches were rejected,
> with this new implementation attempting to fix my understanding of the flaws
> in the older patches

Hi David,

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).

https://lore.kernel.org/linux-nvme/20240129181953.1183084-1-jallison@ciq.com/

As your work is very similar (although has some of the same problems
that people already asked me to fix in earlier versions of the code)
maybe we can collaborate on getting a unified version of this work
reviewed.

Please take a look at the link above, and see if we can merge our efforts.

Thanks !

Jeremy Allison / CIQ.
Samba Team.

             reply	other threads:[~2024-02-07 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 20:34 Jeremy Allison [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-07 20:40 [RFC PATCH 0/6] async device shutdown support Jeremy Allison
2024-02-19  7:31 ` Lukas Wunner
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=CADfv6Ka0M947muKa7hSuVv5Ot_tonmFNBYyrkzCQ5_KUVqN6YQ@mail.gmail.com \
    --to=jallison@ciq.com \
    --cc=djeffery@redhat.com \
    --cc=hch@lst.de \
    --cc=jra@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=rafael@kernel.org \
    --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).