From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: netdev@vger.kernel.org, jgarzik@pobox.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] gianfar: Add I/O barriers when touching buffer descriptor ownership.
Date: Wed, 02 May 2007 15:40:20 -0500 [thread overview]
Message-ID: <4638F734.2040809@freescale.com> (raw)
In-Reply-To: <FA9554A4-5A7D-4E03-BE28-C4B6B80D9DB9@kernel.crashing.org>
Kumar Gala wrote:
> On May 2, 2007, at 3:12 PM, Scott Wood wrote:
>> wmb() is a sync, smp_wmb() is an eieio. Andy told me he would not
>> accept a sync in those spots.
>
>
> Sorry, was looking at the iobarrier code.
>
>> And the driver is already ppc-specific; it uses in/out_be32.
>
>
> True, but its hidden behind the gfar_read/write accessors.
>
> Your change is a bit more blatant.
Well, Segher doesn't want me to use iobarrier (because it's not I/O).
Andy doesn't want me to use wmb() (because it's sync). I don't think
something like gfar_wmb() would be appropriate. So the remaining
options are either eieio(), or a new non-arch-specific,
non-driver-specific mem_wmb() (or whatever).
While I like the latter option, I don't think this bugfix should have to
wait for it.
-Scott
next prev parent reply other threads:[~2007-05-02 20:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 19:57 [PATCH v2] gianfar: Add I/O barriers when touching buffer descriptor ownership Scott Wood
2007-05-02 20:09 ` Kumar Gala
2007-05-02 20:12 ` Scott Wood
2007-05-02 20:20 ` Kumar Gala
2007-05-02 20:40 ` Scott Wood [this message]
2007-05-02 21:23 ` Kumar Gala
2007-05-02 21:30 ` Scott Wood
2007-05-03 2:10 ` Kumar Gala
2007-05-03 16:00 ` Scott Wood
2007-05-03 16:38 ` Segher Boessenkool
2007-05-02 23:42 ` Segher Boessenkool
2007-05-04 22:13 ` Linas Vepstas
2007-05-04 23:24 ` Olof Johansson
2007-05-05 0:41 ` Segher Boessenkool
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=4638F734.2040809@freescale.com \
--to=scottwood@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
/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).