Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760116AbZKFWKz (ORCPT ); Fri, 6 Nov 2009 17:10:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760095AbZKFWKt (ORCPT ); Fri, 6 Nov 2009 17:10:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:15067 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759934AbZKFWKr (ORCPT ); Fri, 6 Nov 2009 17:10:47 -0500 Date: Fri, 6 Nov 2009 17:10:19 -0500 From: Vivek Goyal To: Gui Jianfeng Cc: linux-kernel@vger.kernel.org, jens.axboe@oracle.com, nauman@google.com, dpshah@google.com, lizf@cn.fujitsu.com, ryov@valinux.co.jp, fernando@oss.ntt.co.jp, s-uchida@ap.jp.nec.com, taka@valinux.co.jp, jmoyer@redhat.com, balbir@linux.vnet.ibm.com, righi.andrea@gmail.com, m-ikeda@ds.jp.nec.com, akpm@linux-foundation.org, riel@redhat.com, kamezawa.hiroyu@jp.fujitsu.com Subject: Re: [PATCH 15/20] blkio: Take care of preemptions across groups Message-ID: <20091106221019.GA2969@redhat.com> References: <1257291837-6246-1-git-send-email-vgoyal@redhat.com> <1257291837-6246-16-git-send-email-vgoyal@redhat.com> <4AF3D68E.3050203@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AF3D68E.3050203@cn.fujitsu.com> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2763 Lines: 80 On Fri, Nov 06, 2009 at 03:55:58PM +0800, Gui Jianfeng wrote: > Vivek Goyal wrote: > > o Additional preemption checks for groups where we travel up the hierarchy > > and see if one queue should preempt other or not. > > > > o Also prevents preemption across groups in some cases to provide isolation > > between groups. > > > > Signed-off-by: Vivek Goyal > > --- > > block/cfq-iosched.c | 33 +++++++++++++++++++++++++++++++++ > > 1 files changed, 33 insertions(+), 0 deletions(-) > > > > diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c > > index 87b1799..98dbead 100644 > > --- a/block/cfq-iosched.c > > +++ b/block/cfq-iosched.c > > @@ -2636,6 +2636,36 @@ cfq_update_idle_window(struct cfq_data *cfqd, struct cfq_queue *cfqq, > > } > > } > > > > +static bool cfq_should_preempt_group(struct cfq_data *cfqd, > > + struct cfq_queue *cfqq, struct cfq_queue *new_cfqq) > > +{ > > + struct cfq_entity *cfqe = &cfqq->entity; > > + struct cfq_entity *new_cfqe = &new_cfqq->entity; > > + > > + if (cfqq_to_cfqg(cfqq) != &cfqd->root_group) > > + cfqe = parent_entity(&cfqq->entity); > > + > > + if (cfqq_to_cfqg(new_cfqq) != &cfqd->root_group) > > + new_cfqe = parent_entity(&new_cfqq->entity); > > + > > + /* > > + * Allow an RT request to pre-empt an ongoing non-RT cfqq timeslice. > > + */ > > + > > + if (new_cfqe->ioprio_class == IOPRIO_CLASS_RT > > + && cfqe->ioprio_class != IOPRIO_CLASS_RT) > > + return true; > > + /* > > + * Allow an BE request to pre-empt an ongoing IDLE clas timeslice. > > + */ > > + > > + if (new_cfqe->ioprio_class == IOPRIO_CLASS_BE > > + && cfqe->ioprio_class == IOPRIO_CLASS_IDLE) > > + return true; > > + > > + return false; > > +} > > + > > /* > > * Check if new_cfqq should preempt the currently active queue. Return 0 for > > * no or if we aren't sure, a 1 will cause a preempt. > > @@ -2666,6 +2696,9 @@ cfq_should_preempt(struct cfq_data *cfqd, struct cfq_queue *new_cfqq, > > if (rq_is_sync(rq) && !cfq_cfqq_sync(cfqq)) > > return true; > > > > + if (cfqq_to_cfqg(new_cfqq) != cfqq_to_cfqg(cfqq)) > > + return cfq_should_preempt_group(cfqd, cfqq, new_cfqq); > > + > > Vivek, why not put cfq_should_preempt_group() at the beginning of cfq_should_preempt() > to prevent preemption across groups? Hi Gui, Currently the checks before the group check were not hurting much, that's why. The only contentious check will be if a sync IO in one group should preempt the async IO in other group or not. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/