Re: [LSF/MM ATTEND AND AGENDA TOPIC] request to attend the summit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[...]

>
> I agree that it would be useful to discuss blk-mq I/O scheduling during
> LSF/MM. However, blk-mq I/O scheduling involves more than what has been
> described above. The topics I would like to see being discussed are:
> * How to add an I/O scheduling API to the blk-mq core. This is what Jens
>   is working on (http://git.kernel.dk/cgit/linux-block/log/?h=blk-mq-sched).
> * The BFQ for blk-mq patch series once this patch series has been posted.
>   If the rules for this edition of LSF/MM are similar to those of previous
>   editions then I expect that the LSF/MM program committee will want to
>   see a BFQ for blk-mq implementation posted as patches on a Linux kernel
>   mailing list before adding a session about BFQ for blk-mq to the LSF/MM
>   agenda.
> * Since BFQ has been designed for hard disks and since the approach in BFQ
>   for handling deceptive idleness reduces bandwidth, what scheduling
>   algorithm to use for storage media that do not have any moving parts
>   (SSDs and MMC).
> * How to port the MMC driver to blk-mq. See also Linus Walleij, "[PATCH
>   v2] RFD: switch MMC/SD to use blk-mq multiqueueing"
>   (https://www.spinics.net/lists/linux-block/msg07360.html).

Hi Bart,

As the MMC maintainer I am also interested in participating in all the
above BFQ/MMC related discussions.

Regarding the blk-mq port for MMC, I would also like to add a detail,
which perhaps may influence the generic blkmq interface.

The MMC block device driver implements a asynchronous request
mechanism, which increases performance for architectures where DMA
mapping operations are slow (cache flushes/bounce buffering when using
non-coherent DMAs). Ideally I would like to remove this hack from the
MMC subsystem, if it makes sense to extend blkmq to support this. And
if not, perhaps we can discuss on the best method to implement it for
MMC.

Kind regards
Uffe
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux