linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-block@vger.kernel.org,
	Paolo Valente <paolo.valente@linaro.org>
Subject: Re: [PATCH] memstick: core: Imply IOSCHED_BFQ
Date: Thu, 2 Feb 2023 11:04:32 -0700	[thread overview]
Message-ID: <f6fcf969-7f66-17dd-f9e5-df68786e229f@kernel.dk> (raw)
In-Reply-To: <CAPDyKFqCMZLOte6Fd6oJgTMXaMYMTiRsZKSJu-YJE+nWYTpQ6g@mail.gmail.com>

On 2/2/23 8:22 AM, Ulf Hansson wrote:
> On Tue, 31 Jan 2023 at 09:52, Linus Walleij <linus.walleij@linaro.org> wrote:
>>
>> If we enable the memory stick block layer, use Kconfig to imply
>> the BFQ I/O scheduler.
>>
>> As all memstick devices are single-queue, this is the scheduler that
>> users want so let's be helpful and make sure it gets
>> default-selected into a manual kernel configuration. It will still
>> need to be enabled at runtime (usually with udev scripts).
>>
>> Cc: linux-block@vger.kernel.org
>> Cc: Paolo Valente <paolo.valente@linaro.org>
>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> 
> For the similar reasons to why I applied the MMC patch, applied for
> next, thanks!

And a bad idea, for the exact same reasons...

-- 
Jens Axboe



      reply	other threads:[~2023-02-02 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  8:52 [PATCH] memstick: core: Imply IOSCHED_BFQ Linus Walleij
2023-01-31  9:01 ` Christoph Hellwig
2023-01-31 17:09 ` Bart Van Assche
2023-02-02 15:22 ` Ulf Hansson
2023-02-02 18:04   ` Jens Axboe [this message]

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=f6fcf969-7f66-17dd-f9e5-df68786e229f@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --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).