From: Ming Lei <ming.lei@redhat.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Faiz Abbas <faiz_abbas@ti.com>,
linux-block <linux-block@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] mmc: align max segment size with logical block size
Date: Wed, 27 Feb 2019 23:50:44 +0800 [thread overview]
Message-ID: <20190227155044.GB10141@ming.t460p> (raw)
In-Reply-To: <CAPDyKFqMz3M8SzupEHP_k=r=r8wJ_dKYQRP=LMoRFUbq60E3Sg@mail.gmail.com>
On Wed, Feb 27, 2019 at 02:57:04PM +0100, Ulf Hansson wrote:
> + Christoph
>
> On Wed, 27 Feb 2019 at 14:02, Ming Lei <ming.lei@redhat.com> wrote:
> >
> > Logical block size is the lowest possible block size that the storage
> > device can address. Max segment size is often related with controller's
> > DMA capability. And it is reasonable to align max segment size with
> > logical block size.
> >
> > SDHCI sets un-aligned max segment size, and causes ADMA error, so
> > fix it by aligning max segment size with logical block size.
>
> Seems reasonable. However, is this specific to MMC or should it be
> managed in block layer?
So far, only see such broken max segment size on MMC, so suggest to
fix in MMC, otherwise we may have to align the limit in fast path.
>
> >
> > Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> > Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
> > Cc: Faiz Abbas <faiz_abbas@ti.com>
> > Cc: linux-block@vger.kernel.org
> > Signed-off-by: Ming Lei <ming.lei@redhat.com>
> > ---
> > drivers/mmc/core/block.c | 6 ------
> > drivers/mmc/core/queue.c | 9 ++++++++-
> > 2 files changed, 8 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c
> > index 14f3fdb8c6bb..9ce8eb51a60f 100644
> > --- a/drivers/mmc/core/block.c
> > +++ b/drivers/mmc/core/block.c
> > @@ -2380,12 +2380,6 @@ static struct mmc_blk_data *mmc_blk_alloc_req(struct mmc_card *card,
> > snprintf(md->disk->disk_name, sizeof(md->disk->disk_name),
> > "mmcblk%u%s", card->host->index, subname ? subname : "");
> >
> > - if (mmc_card_mmc(card))
> > - blk_queue_logical_block_size(md->queue.queue,
> > - card->ext_csd.data_sector_size);
> > - else
> > - blk_queue_logical_block_size(md->queue.queue, 512);
> > -
> > set_capacity(md->disk, size);
> >
> > if (mmc_host_cmd23(card->host)) {
> > diff --git a/drivers/mmc/core/queue.c b/drivers/mmc/core/queue.c
> > index cc19e71c71d4..891bdbe14192 100644
> > --- a/drivers/mmc/core/queue.c
> > +++ b/drivers/mmc/core/queue.c
> > @@ -355,6 +355,7 @@ static void mmc_setup_queue(struct mmc_queue *mq, struct mmc_card *card)
> > {
> > struct mmc_host *host = card->host;
> > u64 limit = BLK_BOUNCE_HIGH;
> > + unsigned block_size = 512;
> >
> > if (mmc_dev(host)->dma_mask && *mmc_dev(host)->dma_mask)
> > limit = (u64)dma_max_pfn(mmc_dev(host)) << PAGE_SHIFT;
> > @@ -368,7 +369,13 @@ static void mmc_setup_queue(struct mmc_queue *mq, struct mmc_card *card)
> > blk_queue_max_hw_sectors(mq->queue,
> > min(host->max_blk_count, host->max_req_size / 512));
> > blk_queue_max_segments(mq->queue, host->max_segs);
> > - blk_queue_max_segment_size(mq->queue, host->max_seg_size);
> > +
> > + if (mmc_card_mmc(card))
> > + block_size = card->ext_csd.data_sector_size;
> > +
> > + blk_queue_logical_block_size(mq->queue, block_size);
> > + blk_queue_max_segment_size(mq->queue, host->max_seg_size &
> > + ~(block_size - 1));
>
> Can't we use round_down() instead? No?
Sure, use round_down() in V2.
thanks,
Ming
prev parent reply other threads:[~2019-02-27 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 13:02 [PATCH] mmc: align max segment size with logical block size Ming Lei
2019-02-27 13:57 ` Ulf Hansson
2019-02-27 15:50 ` 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=20190227155044.GB10141@ming.t460p \
--to=ming.lei@redhat.com \
--cc=faiz_abbas@ti.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=naresh.kamboju@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