From: Jens Axboe <axboe@suse.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] new fifo I/O elevator that really does nothing at all
Date: Wed, 13 Apr 2005 09:45:10 +0200 [thread overview]
Message-ID: <20050413074509.GF20044@suse.de> (raw)
In-Reply-To: <200504121758.j3CHwQg11702@unix-os.sc.intel.com>
On Tue, Apr 12 2005, Chen, Kenneth W wrote:
> Chen, Kenneth W wrote on Tuesday, April 05, 2005 5:13 PM
> > Jens Axboe wrote on Tuesday, April 05, 2005 7:54 AM
> > > On Tue, Mar 29 2005, Chen, Kenneth W wrote:
> > > > Jens Axboe wrote on Tuesday, March 29, 2005 12:04 PM
> > > > > No such promise was ever made, noop just means it does 'basically
> > > > > nothing'. It never meant FIFO in anyway, we cannot break the semantics
> > > > > of block layer commands just for the hell of it.
> > > >
> > > > Acknowledged and understood, will try your patch shortly.
> > >
> > > Did you test it?
> >
> > Experiment is in the queue, should have a result in a day or two.
>
>
> Jens, your patch works! We are seeing a little bit increase in
Super.
> indirect branch calls with your patch where our patch tries to remove
> elevator_merge_fn() completely. But the difference is all within
> noise range.
Yeah that is expected. Thanks for testing!
> If there is no other issues (I don't see any), we would like to see
> this patch merged upstream. Thanks.
I will pass it along.
--
Jens Axboe
next prev parent reply other threads:[~2005-04-13 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7A4826DE8867D411BAB8009027AE9EB91DB47626@scsmsx401.amr.corp.intel.com>
2005-04-12 17:58 ` [patch] new fifo I/O elevator that really does nothing at all Chen, Kenneth W
2005-04-13 7:45 ` Jens Axboe [this message]
2005-03-29 1:48 Chen, Kenneth W
2005-03-29 8:06 ` Jens Axboe
2005-03-29 18:50 ` Chen, Kenneth W
2005-03-29 20:04 ` Jens Axboe
2005-03-29 20:07 ` Chen, Kenneth W
2005-04-05 14:54 ` Jens Axboe
2005-04-06 0:12 ` Chen, Kenneth W
2005-03-29 22:20 ` Bill Davidsen
2005-03-30 7:13 ` Jens Axboe
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=20050413074509.GF20044@suse.de \
--to=axboe@suse.de \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.