All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, ckrm-tech@lists.sourceforge.net
Subject: Re: [PATCH] cfq-prio #2
Date: Tue, 11 Nov 2003 01:48:10 +1100	[thread overview]
Message-ID: <3FAFA52A.3050600@cyberone.com.au> (raw)
In-Reply-To: <20031110144412.GK32637@suse.de>



Jens Axboe wrote:

>On Tue, Nov 11 2003, Nick Piggin wrote:
>
>>
>>Jens Axboe wrote:
>>
>>
>>>On Tue, Nov 11 2003, Nick Piggin wrote:
>>>
>>>
>>>>>
>>>>Its quite important. If the queue is full, and AS is waiting for a process
>>>>to submit a request, its got a long wait.
>>>>
>>>>Maybe a lower limit for per process nr_requests. Ie. you may queue if this
>>>>queue has less than 128 requests _or_ you have less than 8 requests
>>>>outstanding. This would solve my problem. It would also give you a much 
>>>>more
>>>>appropriate scaling for server workloads, I think. Still, thats quite a
>>>>change in behaviour (simple to code though).
>>>>
>>>>
>>>That basically belongs inside your may_queue for the io scheduler, imo.
>>>
>>>
>>You can force it to disallow the request, but you can't force it to allow
>>one (depending on a successful memory allocation, of course).
>>
>
>Well that's back two mails then, make may_queue return whether you must
>queue, may queue, or can't queue.
>

Yep, sounds good. I'll make a patch for it for 2.6.x > 0 sometime unless
you beat me to it.



  reply	other threads:[~2003-11-10 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 14:00 [PATCH] cfq-prio #2 Jens Axboe
2003-11-10 14:16 ` Nick Piggin
2003-11-10 14:23   ` Jens Axboe
2003-11-10 14:34     ` Nick Piggin
2003-11-10 14:39       ` Jens Axboe
2003-11-10 14:43         ` Nick Piggin
2003-11-10 14:44           ` Jens Axboe
2003-11-10 14:48             ` Nick Piggin [this message]
2003-11-10 14:52               ` 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=3FAFA52A.3050600@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=axboe@suse.de \
    --cc=ckrm-tech@lists.sourceforge.net \
    --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.