From: Oliver Neukum <oliver@neukum.org>
To: linux-usb-devel@lists.sourceforge.net
Cc: Alan Stern <stern@rowland.harvard.edu>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Sven Luther <sven.luther@wanadoo.fr>,
Alan Cox <alan@www.pagan.org.uk>, Nicolas DET <nd@bplan-gmbh.de>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [linux-usb-devel] [Patch] for UHCI driver (from kernel 2.6.6).
Date: Sat, 19 Jun 2004 08:53:26 +0200 [thread overview]
Message-ID: <200406190853.32745.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0406181737520.1334-100000@ida.rowland.org>
Am Freitag, 18. Juni 2004 23:41 schrieb Alan Stern:
> > barriers. Actually, it's worse, you need a full mb() to order them,
> > which is why lately, we made ppc64 writeX() do full sync's ... that sucks
> > but it's near to impossible to get an abstract IO API that would cover
> > our needs here and still make other archs happy it seems...
>
> I recently changed a few mb() calls to wmb(), because they only protected
> data the CPU was writing to be read by the device. Do you think changing
> all the wmb()'s back to mb()'s would make a difference?
Are these issues documented somewhere?
Regards
Oliver
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-06-19 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40CDC05B.9020708@bplan-gmbh.de>
[not found] ` <1087241757.5996.3.camel@localhost.localdomain>
[not found] ` <20040617173454.GA5971@pegasos>
2004-06-18 10:20 ` [linux-usb-devel] [Patch] for UHCI driver (from kernel 2.6.6) Sven Luther
2004-06-18 21:31 ` Benjamin Herrenschmidt
2004-06-18 21:41 ` Alan Stern
2004-06-18 21:43 ` Benjamin Herrenschmidt
2004-06-19 13:59 ` Alan Stern
2004-06-19 14:16 ` Sven Luther
2004-06-21 8:18 ` Segher Boessenkool
2004-06-21 8:57 ` Sven Luther
2004-06-19 6:53 ` Oliver Neukum [this message]
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=200406190853.32745.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=alan@www.pagan.org.uk \
--cc=benh@kernel.crashing.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nd@bplan-gmbh.de \
--cc=stern@rowland.harvard.edu \
--cc=sven.luther@wanadoo.fr \
/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).