public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>,
	John Garry <john.g.garry@oracle.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Keith Busch <kbusch@kernel.org>,
	Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH V2] block: make segment size limit workable for > 4K PAGE_SIZE
Date: Fri, 14 Feb 2025 09:37:10 +0800	[thread overview]
Message-ID: <Z66eRnK7V_lHFe5I@fedora> (raw)
In-Reply-To: <csvt2osvntbtvqveufnsiv2dhinz46z744fx4mgjarbd3twg45@k7zm3jv4k2xb>

On Thu, Feb 13, 2025 at 03:18:43PM +0100, Daniel Gomez wrote:
> On Thu, Feb 13, 2025 at 04:51:55PM +0100, Ming Lei wrote:
> > On Thu, Feb 13, 2025 at 12:30:29AM -0800, Christoph Hellwig wrote:
> > > On Thu, Feb 13, 2025 at 04:02:46PM +0800, Ming Lei wrote:
> > > > The problem[1] is that this kind of mmc card fails to be recognized as
> > > > block disk. Block layer io split code can handle this case actually.
> > > 
> > > When we still had bio_add_pc_page it would break the assumption that
> > > you could always add a full page.  With that gone and everything going
> > > through the split machinery we might be fine now, but backporting it
> > > to 6.13 and earlier will cause breakage.
> >  
> > Yes, I will mention the following two are depended for backporting in
> > commit log:
> > 
> > 02ee5d69e3ba block: remove blk_rq_bio_prep
> > 6aeb4f836480 block: remove bio_add_pc_page
> 
> Ming, is that sufficient for your use case? Or do you still need to remove the
> assumption that the "minimum" segment size is not PAGE_SIZE?

If you want to make any block device with < 64K max_segment_size working
on 64K page_size kernel, you need this patch and the following three
dependencies:

commit 6aeb4f836480 ("block: remove bio_add_pc_page")
commit 02ee5d69e3ba ("block: remove blk_rq_bio_prep")
commit b7175e24d6ac ("block: add a dma mapping iterator")


Thanks,
Ming


  reply	other threads:[~2025-02-14  1:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10  9:03 [PATCH V2] block: make segment size limit workable for > 4K PAGE_SIZE Ming Lei
2025-02-10 12:14 ` Hannes Reinecke
2025-02-10 13:26   ` Ming Lei
2025-02-10 20:17 ` Luis Chamberlain
2025-02-11  2:10   ` Ming Lei
2025-02-13  7:34     ` Daniel Gomez
2025-02-13  8:02       ` Ming Lei
2025-02-13  8:30         ` Christoph Hellwig
2025-02-13  8:51           ` Ming Lei
2025-02-13 14:18             ` Daniel Gomez
2025-02-14  1:37               ` Ming Lei [this message]
2025-02-13  8:33 ` Christoph Hellwig
2025-02-13  8:45 ` John Garry
2025-02-13  9:58   ` Ming Lei
2025-02-13 10:23     ` John Garry
2025-02-13 10:35       ` Ming Lei
2025-02-13 11:12         ` John Garry
2025-02-13 11:33           ` Ming Lei
2025-02-13 11:41             ` John Garry
2025-02-14  9:38 ` Daniel Gomez
2025-02-14 11:19   ` Ming Lei
2025-02-14 12:28     ` Daniel Gomez
2025-02-14 12:51       ` Ming Lei

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=Z66eRnK7V_lHFe5I@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=da.gomez@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=hch@infradead.org \
    --cc=john.g.garry@oracle.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --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