public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: "Li, Shaohua" <shaohua.li@intel.com>
Cc: Gui Jianfeng <guijianfeng@cn.fujitsu.com>,
	Corrado Zoccolo <czoccolo@gmail.com>,
	"jens.axboe@oracle.com" <jens.axboe@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jmoyer@redhat.com" <jmoyer@redhat.com>,
	"yanmin_zhang@linux.intel.com" <yanmin_zhang@linux.intel.com>
Subject: Re: [PATCH]cfq-iosched: don't stop async queue with async requests pending
Date: Tue, 19 Jan 2010 17:33:56 -0500	[thread overview]
Message-ID: <20100119223356.GC4992@redhat.com> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD926511499ACE22B@shzsmsx501.ccr.corp.intel.com>

On Tue, Jan 19, 2010 at 08:52:01AM +0800, Li, Shaohua wrote:

[..]
> >Yes cfq_should_idle() can check for async queue and return false.
> >
> >Regarding group loosing fair share, currently all async queues are in root
> >group and not in individual groups, so this particular change should not
> >affect a lot. We will continue to idle on sync-idle and sync-noidle
> >service tree. Only async service tree is the exception.
> >
> >Once we introduce per group async queue in future, we shall have to come
> >up with something else, if need be.
> >
> >So keep this as a separate patch. I think in the presence of mixed
> >workload, (readers and buffered writers), it might give little performance
> >boost. We need to test it though.
> Ok, if you thought this method doesn't break group, here is the updated
> patch. I'm sorry to send the attached patch, my mailbox has trouble.

Hi Shaohua,

I did some testing on cfq group functionality and I did not see any
significant impact of this patch.

I am yet to write some test cases for mixed workload testing and see the
impact of this patch. Will get back to you soon.

Thanks
Vivek

  reply	other threads:[~2010-01-19 22:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13  7:44 [PATCH]cfq-iosched: don't stop async queue with async requests pending Shaohua Li
2010-01-13  8:18 ` Corrado Zoccolo
2010-01-13  8:23   ` Shaohua Li
2010-01-13 11:13     ` Vivek Goyal
2010-01-14  3:41       ` Shaohua Li
2010-01-14  5:27         ` Gui Jianfeng
2010-01-14  6:17           ` Shaohua Li
2010-01-14  8:21             ` Gui Jianfeng
2010-01-14  9:04               ` Shaohua Li
2010-01-14 11:09             ` Vivek Goyal
2010-01-19  0:52               ` Li, Shaohua
2010-01-19 22:33                 ` Vivek Goyal [this message]
2010-01-13 11:10 ` Vivek Goyal
2010-01-13 21:30   ` Corrado Zoccolo
2010-01-13 22:26     ` Vivek Goyal
2010-01-14  2:46 ` Gui Jianfeng
2010-01-14  3:43   ` Shaohua Li

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=20100119223356.GC4992@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=czoccolo@gmail.com \
    --cc=guijianfeng@cn.fujitsu.com \
    --cc=jens.axboe@oracle.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=yanmin_zhang@linux.intel.com \
    /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