LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Nikanth Karthikesan <knikanth@suse.de>
To: linux-kernel@vger.kernel.org
Cc: axboe@kernel.dk, nickpiggin@yahoo.com.au
Subject: Re: [PATCH] [RFC] block/elevator: change nr_requests handling
Date: Tue, 29 Jan 2008 23:17:04 +0530	[thread overview]
Message-ID: <1201628824.16911.0.camel@nikanth-laptop.blr.novell.com> (raw)
In-Reply-To: <1201627774.14644.5.camel@nikanth-laptop.blr.novell.com>

On Tue, 2008-01-29 at 22:59 +0530, Nikanth Karthikesan wrote:

> Check for nr_requests only when io schedulers dispatch
> 
> Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
> 

Jens,

The patch is against 2.6.24. Before the block/ll_rw_blk.c splitup.

Thanks
Nikanth


  reply	other threads:[~2008-01-29 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 17:29 Nikanth Karthikesan
2008-01-29 17:47 ` Nikanth Karthikesan [this message]
2008-01-29 18:19 ` Jens Axboe
2008-01-30 13:53   ` Nikanth Karthikesan
2008-01-30 13:56     ` 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=1201628824.16911.0.camel@nikanth-laptop.blr.novell.com \
    --to=knikanth@suse.de \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --subject='Re: [PATCH] [RFC] block/elevator: change nr_requests handling' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).