From: Jens Axboe <axboe@kernel.dk>
To: merez@codeaurora.org
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
DOCUMENTATION <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/3] block: Add test-iosched scheduler
Date: Tue, 31 Jul 2012 17:46:22 +0200 [thread overview]
Message-ID: <5017FDCE.5030700@kernel.dk> (raw)
In-Reply-To: <09c3a301ad7ca4fa396c4d00615312c1.squirrel@www.codeaurora.org>
On 07/31/2012 04:36 PM, merez@codeaurora.org wrote:
> Hi Jens,
>
> Do you have comments on this patch?
> Can we push it to kernel 3.6 version?
I have questions - what is this good for? In other words, explain to me
why this is useful code. And in particular why this cannot be done from
userspace with bsg and block tracing?
IOW, I'm dubious as to whether a new _io scheduler_ is the correct
solution to the problem you have at hand.
--
Jens Axboe
next prev parent reply other threads:[~2012-07-31 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 14:25 [PATCH v5 1/3] block: Add test-iosched scheduler Maya Erez
2012-07-31 14:36 ` merez
2012-07-31 15:46 ` Jens Axboe [this message]
2012-08-02 13:16 ` merez
2012-08-28 6:36 ` merez
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=5017FDCE.5030700@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=merez@codeaurora.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).