From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
"'Andrew Morton'" <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Cache queue_congestion_on/off_threshold
Date: Tue, 11 May 2004 00:43:28 +1000 [thread overview]
Message-ID: <409F9510.9050001@yahoo.com.au> (raw)
In-Reply-To: <20040510143024.GF14403@suse.de>
Jens Axboe wrote:
> On Fri, May 07 2004, Chen, Kenneth W wrote:
>
>>>>>>Jens Axboe wrote on Friday, May 07, 2004 2:39 AM
>>>
>>>On Thu, May 06 2004, Chen, Kenneth W wrote:
>>>
>>>>(3) can we allocate request structure up front in __make_request?
>>>> For I/O that cannot be merged, the elevator code executes twice
>>>> in __make_request.
>>>>
>>>
>>>Actually, with the good working batching we might get away with killing
>>>freereq completely. Have you tested that (if not, could you?)
>>
>>Sorry, I'm clueless on "good working batching". If you could please give
>>me some pointers, I will definitely test it.
>
>
> Something like this.
>
While we're doing that can we drop the GFP_ATOMIC allocation
completely?
next prev parent reply other threads:[~2004-05-10 14:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 22:12 Cache queue_congestion_on/off_threshold Chen, Kenneth W
2004-05-06 6:20 ` Jens Axboe
2004-05-06 6:34 ` Andrew Morton
2004-05-06 6:43 ` Jens Axboe
2004-05-06 20:30 ` Chen, Kenneth W
2004-05-07 3:02 ` Andrew Morton
2004-05-07 9:35 ` Jens Axboe
2004-05-06 20:29 ` Chen, Kenneth W
2004-05-07 9:39 ` Jens Axboe
2004-05-07 22:00 ` Chen, Kenneth W
2004-05-10 14:30 ` Jens Axboe
2004-05-10 14:43 ` Nick Piggin [this message]
2004-05-10 14:44 ` Jens Axboe
2004-05-11 3:22 ` Nick Piggin
2004-05-12 5:32 ` Chen, Kenneth W
2004-05-12 7:05 ` Jens Axboe
2004-05-12 13:48 ` Jens Axboe
2004-05-12 14:22 ` 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=409F9510.9050001@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox