From: Christoph Hellwig <hch@infradead.org>
To: 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: Sun, 28 Feb 2016 08:13:43 -0800 [thread overview]
Message-ID: <20160228161343.GA22246@infradead.org> (raw)
In-Reply-To: <20160226161052.GA4089@suselix.suse.de>
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.
next prev parent reply other threads:[~2016-02-28 16:13 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 ` Christoph Hellwig [this message]
2016-02-29 0:21 ` [Lsf-pc] " Hannes Reinecke
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=20160228161343.GA22246@infradead.org \
--to=hch@infradead.org \
--cc=aherrmann@suse.com \
--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).