Subject: Re: [PATCH] kmalloc_percpu
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Andrew Morton <akpm@digeo.com>
Cc: "David S. Miller" <davem@redhat.com>, rusty@rustcorp.com.au,
       dipankar@in.ibm.com, linux-kernel@vger.kernel.org
In-Reply-To: <20030505235758.25f769fc.akpm@digeo.com>
References: <20030505.211606.28803580.davem@redhat.com>
	 <20030505224815.07e5240c.akpm@digeo.com>
	 <20030505234248.7cc05f43.akpm@digeo.com>
	 <20030505.223944.23027730.davem@redhat.com>
	 <20030505235758.25f769fc.akpm@digeo.com>
Content-Type: text/plain
Organization: 
Message-Id: <1052237149.25671.1.camel@serpentine.internal.keyresearch.com>
Mime-Version: 1.0
Date: 06 May 2003 09:05:49 -0700
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 684
Lines: 17

On Mon, 2003-05-05 at 23:57, Andrew Morton wrote:

> The disk_stats structure has an "in flight" member.  If we don't have proper
> locking around that, disks will appear to have -3 requests in flight for all
> time, which would look a tad odd.

For what it's worth, the disk stats patch that vendors have been
shipping forever with 2.4 (and that Christoph pushed into 2.4.20) has
this problem, so at least people will be used to it.

	<b

-
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/