From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] s2io ppc64 fix for readq/writeq
Date: Mon, 06 Nov 2006 19:52:58 +1100 [thread overview]
Message-ID: <1162803178.28571.300.camel@localhost.localdomain> (raw)
In-Reply-To: <454EF07B.4010503@pobox.com>
> This is why I said "good enough for drivers". This is _key_.
>
> I have run into several [PCI] devices with 64-bit registers, and
> __none__ of them had requirements such that the Linux platform code
> -must- provide an atomic readq/writeq. Probably because everybody wants
> to support 32-bit platforms with their devices.
>
> What you call "fairly bogus" is precisely what drivers need. These
> devices with 64-bit registers just don't need the atomicity that arch
> developers harp about :)
Is there any consistency in that case in which half need to be
read/written first ? Or none of these ever had side effects ?
Ben.
next prev parent reply other threads:[~2006-11-06 8:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 2:28 [PATCH] s2io ppc64 fix for readq/writeq Benjamin Herrenschmidt
2006-11-06 7:50 ` Jeff Garzik
2006-11-06 8:04 ` Benjamin Herrenschmidt
2006-11-06 8:21 ` Jeff Garzik
2006-11-06 8:52 ` Benjamin Herrenschmidt [this message]
2006-11-06 9:34 ` Jeff Garzik
2006-11-07 0:17 ` Benjamin Herrenschmidt
2006-11-06 9:37 ` Linus Torvalds
2006-11-06 9:42 ` Benjamin Herrenschmidt
2006-11-06 9:50 ` Linus Torvalds
2006-11-06 9:51 ` Benjamin Herrenschmidt
2006-11-06 9:55 ` Jeff Garzik
2006-11-06 9:57 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-11-06 20:33 Ramkrishna Vepa
2006-11-06 20:46 ` Christoph Hellwig
2006-11-06 20:54 ` Roland Dreier
2006-11-07 2:57 Ramkrishna Vepa
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=1162803178.28571.300.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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).