From: Adrian Hunter <adrian.hunter@intel.com>
To: "Bart Van Assche" <bvanassche@acm.org>,
"Christian Löhle" <CLoehle@hyperstone.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"Christoph Hellwig" <hch@lst.de>
Cc: Avri Altman <Avri.Altman@wdc.com>,
"vincent.whitchurch@axis.com" <vincent.whitchurch@axis.com>
Subject: Re: [PATCH 0/3] mmc: Improve block layer requeueing behavior
Date: Mon, 21 Nov 2022 21:42:39 +0200 [thread overview]
Message-ID: <1c9b3db6-3443-5580-08f2-42520d6a3318@intel.com> (raw)
In-Reply-To: <bade026a-ec83-7516-d5ef-bb373df48a6e@acm.org>
On 21/11/22 21:14, Bart Van Assche wrote:
> On 11/21/22 00:25, Adrian Hunter wrote:
>> On 18/11/22 19:27, Bart Van Assche wrote:
>>> On 11/18/22 02:47, Adrian Hunter wrote:
>>>> Does anyone know why the block layer does not support
>>>> (max_hw_sectors << 9) < PAGE_SIZE ?
>>>
>>> Does this mean that the following patch series would not only be
>>> useful for UFS but also for MMC? "[PATCH 00/10] Support DMA segments
>>> smaller than the page size"
>>> (https://lore.kernel.org/linux-block/20221019222324.362705-1-bvanassche@acm.org/).
>>
>> That patchset still does not allow max_hw_sectors = 1 which is
>> what Christian's case needs.
>
> Hi Adrian,
>
> Why would that patch series not support max_hw_sectors = 1? What am I overlooking?
blk_queue_max_hw_sectors() does not allow it.
next prev parent reply other threads:[~2022-11-21 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 7:30 [PATCH 0/3] mmc: Improve block layer requeueing behavior Christian Löhle
2022-11-18 10:47 ` Adrian Hunter
2022-11-18 17:27 ` Bart Van Assche
2022-11-21 8:25 ` Adrian Hunter
2022-11-21 19:14 ` Bart Van Assche
2022-11-21 19:42 ` Adrian Hunter [this message]
2022-11-21 20:00 ` Bart Van Assche
2022-11-22 7:21 ` Avri Altman
2022-11-22 19:29 ` Bart Van Assche
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=1c9b3db6-3443-5580-08f2-42520d6a3318@intel.com \
--to=adrian.hunter@intel.com \
--cc=Avri.Altman@wdc.com \
--cc=CLoehle@hyperstone.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vincent.whitchurch@axis.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