From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: "Ronny V. Vindenes" <s864@ii.uib.no>,
ck@vds.kolivas.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: CFQ v2 high cpu load fix(?)
Date: Tue, 12 Oct 2004 23:50:05 +1000 [thread overview]
Message-ID: <416BE10D.5040208@yahoo.com.au> (raw)
In-Reply-To: <20041012132214.GA24931@suse.de>
Jens Axboe wrote:
> On Tue, Oct 12 2004, Nick Piggin wrote:
>>Cool. Can you queue up a patch for when -mm opens again, or shall I?
>>I can't imagine it should cause any problems but a bit of testing
>>would be wise.
>
>
> Testing is always good, but maybe Andrew can take it now but just not
> feed to Linus until after 2.6.9?
>
If Andrew doesn't mind, then yeah that would be nice.
next prev parent reply other threads:[~2004-10-12 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 11:16 CFQ v2 high cpu load fix(?) Ronny V. Vindenes
2004-10-12 11:26 ` Nick Piggin
2004-10-12 12:12 ` Jens Axboe
2004-10-12 12:30 ` Nick Piggin
2004-10-12 13:22 ` Jens Axboe
2004-10-12 13:50 ` Nick Piggin [this message]
2004-10-12 20:44 ` Prakash K. Cheemplavam
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=416BE10D.5040208@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s864@ii.uib.no \
/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