From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Oddities in brd queue limits
Date: Tue, 2 Apr 2024 15:41:23 +0200 [thread overview]
Message-ID: <20240402134123.GA32562@lst.de> (raw)
In-Reply-To: <985db17d-691a-4674-8e2d-962ac9a8af1f@suse.de>
On Tue, Apr 02, 2024 at 03:21:00PM +0200, Hannes Reinecke wrote:
> So is it a hard limit (as in: we cannot send I/O smaller than that)
> or a soft limit (as in: we should not send I/O smaller than that)?
It is a completely soft hint that isn't used by anything in the
kernel I/O path.
(as a quick grep would tell..)
prev parent reply other threads:[~2024-04-02 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 13:17 Oddities in brd queue limits Hannes Reinecke
2024-04-02 13:18 ` Christoph Hellwig
2024-04-02 13:21 ` Hannes Reinecke
2024-04-02 13:41 ` Christoph Hellwig [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=20240402134123.GA32562@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.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 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.