From: Jeff Garzik <jgarzik@pobox.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@osdl.org>, netdev@vger.kernel.org
Subject: Re: [PATCH] s2io ppc64 fix for readq/writeq
Date: Mon, 06 Nov 2006 04:55:04 -0500 [thread overview]
Message-ID: <454F0678.50706@pobox.com> (raw)
In-Reply-To: <1162806691.28571.311.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> On Mon, 2006-11-06 at 01:50 -0800, Linus Torvalds wrote:
>> On Mon, 6 Nov 2006, Benjamin Herrenschmidt wrote:
>>> Anyway, what do you think of Jeff proposal to just implement them as two
>>> 32 bits operations ? My arch guy side screams at the idea, but if,
>>> indeed, drivers generally cope fine with it, I suppose that's ok.
>> Last I saw, that's how normal PCI will split the IO anyway, so I guess it
>> makes sense.
>
> Hrm.. true indeed. I'll implement them that way for ppc32 then.
Bonus points if you want to find-and-kill where individual drivers did
#ifndef readq
implement readq and writeq by hand...
#endif
:)
next prev parent reply other threads:[~2006-11-06 9:55 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
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 [this message]
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=454F0678.50706@pobox.com \
--to=jgarzik@pobox.com \
--cc=benh@kernel.crashing.org \
--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).