From: John Dykstra <john.dykstra1@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, pcnet32@verizon.net, jeff@garzik.org
Subject: Re: [PATCH net-next-2.6] pcnet32: Remove pointless memory barriers
Date: Wed, 29 Apr 2009 08:48:17 -0500 [thread overview]
Message-ID: <1241012897.7487.12.camel@Maple> (raw)
In-Reply-To: <20090428.221605.71993506.davem@davemloft.net>
On Tue, 2009-04-28 at 22:16 -0700, David Miller wrote:
> Any driver where these things are present usually has them
> there for a reason. Usually it's because the SGI guys really
> did run into real problems without them on their huge
> machines which can reorder PCI MMIO wrt. real memory operations.
Is that relevant when the driver doesn't do any MMIO operations? All
pcnet32 register accesses are via PCI I/O space, as implied by the
commit description.
Descriptors and buffers are, of course, in consistent physical memory.
This patch doesn't touch the barriers associated with those structures.
> I don't feel good applying this at all, given that I see no
> evidence that there has been any investigation into how these
> barriers got there in the first place.
Before sending out this patch, I determined that the MMIO barriers were
added as part of NAPI support. I CCed one of the authors of that patch,
so he could NAK if appropriate. I've added the other author on this
reply.
I knew there'd be questions about whether removing these two barriers
was safe. Submitting the patch seemed the best way to understand why
they were needed, if they are.
-- John
next prev parent reply other threads:[~2009-04-29 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 19:07 [PATCH net-next-2.6] pcnet32: Remove pointless memory barriers John Dykstra
2009-04-29 5:16 ` David Miller
2009-04-29 13:48 ` John Dykstra [this message]
2009-04-29 17:10 ` Don Fry
2009-04-29 19:07 ` John Dykstra
2009-04-29 22:29 ` Francois Romieu
2009-04-30 0:09 ` Don Fry
2009-04-30 0:16 ` John Dykstra
2009-04-30 0:21 ` David Miller
2009-04-30 0:19 ` David Miller
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=1241012897.7487.12.camel@Maple \
--to=john.dykstra1@gmail.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
/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;
as well as URLs for NNTP newsgroup(s).