public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>,
	John Garry <john.g.garry@oracle.com>,
	Keith Busch <kbusch@kernel.org>, Paul Bunyan <pbunyan@redhat.com>,
	Daniel Gomez <da.gomez@kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [PATCH V5] block: make segment size limit workable for > 4K PAGE_SIZE
Date: Thu, 27 Feb 2025 11:31:39 +0800	[thread overview]
Message-ID: <Z7_cm0GHco5LCFVy@fedora> (raw)
In-Reply-To: <253b6cf9-6f17-4a9f-afd8-27204b1e6093@acm.org>

On Wed, Feb 26, 2025 at 09:38:36AM -0800, Bart Van Assche wrote:
> On 2/24/25 6:21 PM, Ming Lei wrote:
> > diff --git a/block/blk.h b/block/blk.h
> > index 90fa5f28ccab..9cf9a0099416 100644
> > --- a/block/blk.h
> > +++ b/block/blk.h
> > @@ -14,6 +14,7 @@
> >   struct elevator_type;
> >   #define	BLK_DEV_MAX_SECTORS	(LLONG_MAX >> 9)
> > +#define	BLK_MIN_SEGMENT_SIZE	4096
> >   /* Max future timer expiry for timeouts */
> >   #define BLK_MAX_TIMEOUT		(5 * HZ)
> 
> Hi Ming,
> 
> Would you agree with reducing BLK_MIN_SEGMENT_SIZE further, e.g. to 2048
> or 1024? Although I'm not aware of any storage devices that need this

We never take < 4096 as min segment size, I'd rather not relax it for
avoiding any potential regression.

But if any kind of real device requires it, we may re-consider to relax
it more.

> change, this change would make it possible to test the new code paths
> introduced by this patch on systems with a 4 KiB page size. I wrote
> blktests tests for the new code paths before I posted my patch series
> "Support limits below the page size"
> (https://lore.kernel.org/linux-block/20230612203314.17820-1-bvanassche@acm.org/).
> The last two patches of that patch series are still needed to run these
> blktests tests.

Indeed, I guess you will re-send the two, and I am glad to review after it is
posed out.



thanks,
Ming


      reply	other threads:[~2025-02-27  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25  2:21 [PATCH V5] block: make segment size limit workable for > 4K PAGE_SIZE Ming Lei
2025-02-25 15:43 ` Jens Axboe
2025-02-26 17:38 ` Bart Van Assche
2025-02-27  3:31   ` Ming Lei [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=Z7_cm0GHco5LCFVy@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=da.gomez@kernel.org \
    --cc=john.g.garry@oracle.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=pbunyan@redhat.com \
    --cc=yi.zhang@redhat.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