linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-block@vger.kernel.org, linux-mmc@vger.kernel.org
Cc: tglx@linutronix.de, Ulf Hansson <ulf.hansson@linaro.org>,
	Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v3 0/2] blk-mq: Allow to complete requests directly
Date: Thu, 25 Nov 2021 12:52:49 +0100	[thread overview]
Message-ID: <20211125115249.fb6g522pl54nulp3@linutronix.de> (raw)
In-Reply-To: <20211025070658.1565848-1-bigeasy@linutronix.de>

On 2021-10-25 09:06:56 [+0200], To linux-block@vger.kernel.org wrote:
> v2…v3:
>  - Align arguments with the begin of the function name
>    (blk_mq_complete_request_direct).
> 
> v1…v2:
>  - Drop the SCSI patch for now.
>  - Make blk_mq_complete_request_direct() call the completion handler
>    directly instead going through struct chain (Jens and hch might had
>    the same in mind).
> 
> This series converts a part from the MMC layer which completes the
> requests from kworker/ preemptible context. Its intention is to avoid
> going through the softirq stack in preemptible context which would
> involve the ksoftirqd in this case.

Ping :)

This still applies on-top on top of -next. No need to repost, right?

Sebastian

  parent reply	other threads:[~2021-11-25 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25  7:06 [PATCH v3 0/2] blk-mq: Allow to complete requests directly Sebastian Andrzej Siewior
2021-10-25  7:06 ` [PATCH v3 1/2] blk-mq: Add blk_mq_complete_request_direct() Sebastian Andrzej Siewior
2021-10-25  7:10   ` Christoph Hellwig
2021-10-25  7:06 ` [PATCH v3 2/2] mmc: core: Use blk_mq_complete_request_direct() Sebastian Andrzej Siewior
2021-11-25 11:52 ` Sebastian Andrzej Siewior [this message]
2021-11-25 16:02 ` [PATCH v3 0/2] blk-mq: Allow to complete requests directly Jens Axboe

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=20211125115249.fb6g522pl54nulp3@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=ulf.hansson@linaro.org \
    /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).