Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756743AbZDPQhi (ORCPT ); Thu, 16 Apr 2009 12:37:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754482AbZDPQha (ORCPT ); Thu, 16 Apr 2009 12:37:30 -0400 Received: from brick.kernel.dk ([93.163.65.50]:60683 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753248AbZDPQh3 (ORCPT ); Thu, 16 Apr 2009 12:37:29 -0400 Date: Thu, 16 Apr 2009 18:37:28 +0200 From: Jens Axboe To: Jerome Marchand Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] block: simplify I/O stat accounting Message-ID: <20090416163728.GS5178@kernel.dk> References: <49E72F19.1030400@redhat.com> <20090416163456.GR5178@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090416163456.GR5178@kernel.dk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1149 Lines: 33 On Thu, Apr 16 2009, Jens Axboe wrote: > On Thu, Apr 16 2009, Jerome Marchand wrote: > > > > This simplifies I/O stat accounting switching code and separates it > > completely from I/O scheduler switch code. > > > > Requests are accounted according to the state of their request queue > > at the time of the request allocation. There is no need anymore to > > flush the request queue when switching I/O accounting state. > > This is cleaner, I like it. I'll apply it, but I'm changing this one: > > > @@ -792,9 +792,10 @@ static struct request *get_request(struct > > request_queue *q, int rw_flags, > > if (priv) > > rl->elvpriv++; > > > > + iostat = blk_queue_io_stat(q) ? REQ_IO_STAT : 0; > > spin_unlock_irq(q->queue_lock); > > to a regular if, I hate these ?: constructs. An if is much more > readable, imho. Grmbl, your patch is line wrapped. Please fix your mailer. -- Jens Axboe -- 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/