From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
Andreas Herrmann <aherrmann@suse.com>
Cc: lsf-pc@lists.linuxfoundation.org, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC][LSF/MM ATTEND] blk-mq and I/O scheduling
Date: Mon, 29 Feb 2016 08:21:37 +0800 [thread overview]
Message-ID: <56D38F11.1010003@suse.de> (raw)
In-Reply-To: <20160228161343.GA22246@infradead.org>
On 02/29/2016 12:13 AM, Christoph Hellwig wrote:
> I was still hoping we'd get your slicing patches in ASAP at least.
> But there are couple more topics here, so I think it would
> still be useful in that case.
>
Actually I have been pondering an alternative approach.
In most cases submit_bio() / submit_bh() is called in a loop, submitting
several bios in one go.
These bios typically refer to a larger piece of memory, so merging
should be trivial here.
However, both submit_bh() and submit_bio() will never convey this
information, so they will be placed on the queue as individual bios.
If we manage to link the generated bios together we can trivially
implement merging, even for the mq case.
One idea here is to add plugging around the callers, or to allow for
linked bios to be submitted.
I see if I can make some tests here.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-02-29 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 16:10 [LSF/MM TOPIC][LSF/MM ATTEND] blk-mq and I/O scheduling Andreas Herrmann
2016-02-28 16:13 ` [Lsf-pc] " Christoph Hellwig
2016-02-29 0:21 ` Hannes Reinecke [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=56D38F11.1010003@suse.de \
--to=hare@suse.de \
--cc=aherrmann@suse.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).