From: Jens Axboe <jens.axboe@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Corrado Zoccolo <czoccolo@gmail.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [PATCH 0/5] cfq-iosched: improve latency for no-idle queues (v3)
Date: Wed, 4 Nov 2009 08:51:52 +0100 [thread overview]
Message-ID: <20091104075152.GX8742@kernel.dk> (raw)
In-Reply-To: <x49aaz3i807.fsf@segfault.boston.devel.redhat.com>
On Tue, Nov 03 2009, Jeff Moyer wrote:
> Jens Axboe <jens.axboe@oracle.com> writes:
>
> > On Tue, Nov 03 2009, Jeff Moyer wrote:
> >> Jens Axboe <jens.axboe@oracle.com> writes:
> >>
> >> > Since for-linus contains conflicting changes, can you and Jeff please
> >> > double check that everything is still in order? The interesting bit here
> >> > is the merge with for-2.6.33 and the coop limit from Shaohua Li. I did
> >> > the straight forward merge, but we likely just need to drop that logic
> >> > since the coop concept is radically different given that we merge and
> >> > break queues in for-2.6.33.
> >>
> >> Yeah, since I changed the meaning of the cfqq_coop flag, a lot of those
> >> tests are just plain wrong. Let me play with it and I'll send you an
> >> incremental patch in a bit.
> >
> > Thanks, here's what I have. It's basically a revert of the commit in
> > question.
>
> Your patch looks like a straight-forward revert. I still think we need
> some guards in place, though. For now, I think we can go with what you
> have, and I'll come up with some other mechanism to deal with this case.
Thanks Jeff, I'll merge it up and we can get things straightened out in
due time.
--
Jens Axboe
prev parent reply other threads:[~2009-11-04 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 21:43 [PATCH 0/5] cfq-iosched: improve latency for no-idle queues (v3) Corrado Zoccolo
2009-10-28 8:27 ` Jens Axboe
[not found] ` <x49zl7c268s.fsf@segfault.boston.devel.redhat.com>
[not found] ` <4e5e476b0910271124r2cf9f9c0l83fdc59b50619202@mail.gmail.com>
[not found] ` <x493a4wsn5c.fsf@segfault.boston.devel.redhat.com>
[not found] ` <x49fx8wbqd0.fsf@segfault.boston.devel.redhat.com>
[not found] ` <4e5e476b0911030042q5963718aj5875c542e6f6cc40@mail.gmail.com>
[not found] ` <x49ocnju35d.fsf@segfault.boston.devel.redhat.com>
[not found] ` <4e5e476b0911030719m425c208cg311f44a91fad8342@mail.gmail.com>
2009-11-03 18:35 ` Fwd: " Corrado Zoccolo
2009-11-03 20:18 ` Jens Axboe
2009-11-03 20:26 ` Jeff Moyer
2009-11-03 20:28 ` Jens Axboe
2009-11-03 22:00 ` Jeff Moyer
2009-11-04 7:51 ` Jens Axboe [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=20091104075152.GX8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=czoccolo@gmail.com \
--cc=jmoyer@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox