From: David Mosberger <davidm@napali.hpl.hp.com>
To: Jes Sorensen <jes@wildopensource.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Bill Davidsen <davidsen@tmr.com>,
David Mosberger-Tang <David.Mosberger@acm.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Intel x86-64 support merge
Date: Fri, 20 Feb 2004 18:07:05 -0800 [thread overview]
Message-ID: <16438.48457.641361.533828@napali.hpl.hp.com> (raw)
In-Reply-To: <yq0vfm2ry2x.fsf@wildopensource.com>
>>>>> On 20 Feb 2004 02:48:06 -0500, Jes Sorensen <jes@wildopensource.com> said:
Jeff> I doubt Win64 bounces for 64-bit PCI hardware, but who knows...
Jes> Just a shame they don't seem to care about performance and allowing
Jes> one to issue SAC cycles when possible.
Careful. You're assuming that the I/O MMU translation is free.
Depending on many details, that may or may not be the case.
The timing couldn't have been better:
http://marc.theaimsgroup.com/?l=linux-ia64&m=107732581008944
Jes> Oh well, guess one just has to buy a real computer.
That's always a good idea.
--david
next prev parent reply other threads:[~2004-02-21 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1qK5k-7g2-67@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-69@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-71@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-73@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-65@gated-at.bofh.it>
2004-02-19 22:06 ` Bill Davidsen
2004-02-20 4:03 ` David Mosberger-Tang
2004-02-20 4:19 ` Jeff Garzik
2004-02-20 7:48 ` Jes Sorensen
2004-02-21 2:07 ` David Mosberger [this message]
[not found] <1qHr5-2tJ-39@gated-at.bofh.it>
[not found] ` <1qHr5-2tJ-37@gated-at.bofh.it>
[not found] ` <1qIZw-6b9-17@gated-at.bofh.it>
[not found] ` <1qJsI-6Be-57@gated-at.bofh.it>
2004-02-19 0:05 ` David Mosberger-Tang
2004-02-19 9:36 ` David Weinehall
[not found] <200402182006.i1IK6CsS022562@hera.kernel.org>
2004-02-18 21:21 ` Arjan van de Ven
2004-02-18 22:57 ` H. Peter Anvin
2004-02-18 23:16 ` Arjan van de Ven
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=16438.48457.641361.533828@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=David.Mosberger@acm.org \
--cc=davidm@hpl.hp.com \
--cc=davidsen@tmr.com \
--cc=jes@wildopensource.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®