From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from clock-tower.bc.nu ([81.2.110.250]:23240 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S268268AbUIPVJx (ORCPT ); Thu, 16 Sep 2004 17:09:53 -0400 Subject: Re: RFC: being more anal about iospace accesses.. From: Alan Cox In-Reply-To: References: <1095287935.1688.4.camel@mulgrave> <20040916023325.GJ642@parcelfarce.linux.theplanet.co.uk> <20040916134152.GK642@parcelfarce.linux.theplanet.co.uk> <4149E5C2.7010008@pobox.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1095365223.23136.48.camel@localhost.localdomain> Mime-Version: 1.0 Date: Thu, 16 Sep 2004 21:07:03 +0100 To: Linus Torvalds Cc: Jeff Garzik , Matthew Wilcox , James Bottomley , Geert Uytterhoeven , Linux Arch list , Al Viro , Andrew Morton , "David S. Miller" List-ID: Right now we have writeb and __writeb() the later of which isn't store ordering but requires the driver author makes an effort to step on a land mine. It does help performance having these in some cases so can't we propogate the same "__" functions on