All of lore.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>,
	Luis Chamberlain <mcgrof@kernel.org>,
	John Garry <john.g.garry@oracle.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] block: make queue limits workable in case of 64K PAGE_SIZE
Date: Thu, 2 Jan 2025 10:49:40 +0800	[thread overview]
Message-ID: <Z3X-xMeMuF8j0RDA@fedora> (raw)
In-Reply-To: <0b423229-f928-4210-9351-dca353071231@acm.org>

On Wed, Jan 01, 2025 at 06:30:30PM -0800, Bart Van Assche wrote:
> On 1/1/25 5:56 PM, Ming Lei wrote:
> > In RH lab, it has been found that max segment size of some mmc card is
> > less than 64K, then this kind of card can't work in case of 64K PAGE_SIZE.
> 
> That means that that MMC card is incompatible with the 64K page size.

Is there any such linux kernel compatibility standard? If yes, please share
it here.

> 
> Additionally, this patch looks wrong to me. There are good reasons why the
> block layer requires that the DMA segment size is at least as large
> as the page size.

Do you think 512byte sector can't be DMAed?

> 
> You may want to take a look at this rejected patch series:
> Bart Van Assche, "PATCH v6 0/8] Support limits below the page size",
> June 2023 (https://lore.kernel.org/linux-block/20230612203314.17820-1-bvanassche@acm.org/).

'502 Bad Gateway' is returned for the above link.

Thanks,
Ming


  reply	other threads:[~2025-01-02  2:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02  1:56 [PATCH] block: make queue limits workable in case of 64K PAGE_SIZE Ming Lei
2025-01-02  2:30 ` Bart Van Assche
2025-01-02  2:49   ` Ming Lei [this message]
2025-01-02  3:46     ` Bart Van Assche
2025-01-03  2:01       ` Ming Lei
2025-01-03 22:12         ` Bart Van Assche
2025-01-04  1:47           ` Luis Chamberlain
2025-01-04  2:15             ` Bart Van Assche
2025-01-04  4:04               ` Luis Chamberlain
2025-01-04 22:30                 ` Bart Van Assche
2025-01-08 19:32                   ` Luis Chamberlain
2025-01-05  0:59                 ` Keith Busch
2025-01-08 19:12                   ` Luis Chamberlain
2025-01-06  1:20           ` 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=Z3X-xMeMuF8j0RDA@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=john.g.garry@oracle.com \
    --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 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.