public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: davidm@mostang.com (David Mosberger-Tang)
To: Bill Davidsen <davidsen@tmr.com>
Cc: 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: Thu, 19 Feb 2004 20:03:10 -0800	[thread overview]
Message-ID: <16437.34558.298388.89482@panda.mostang.com> (raw)
In-Reply-To: <40353382.8010505@tmr.com>

>>>>> On Thu, 19 Feb 2004 17:06:58 -0500, Bill Davidsen <davidsen@tmr.com> said:

  Bill> David Mosberger-Tang wrote:
  >>>>>>> On Thu, 19 Feb 2004 00:40:24 +0100, Arjan van de Ven
  >>>>>>> <arjan@fenrus.demon.nl> said:
  >>
  Arjan> On Wed, 2004-02-18 at 23:57, H. Peter Anvin wrote:
  >> >> Because they were caught by surprise and just hacked the chips
  >> >> they had in the pipeline, presumably.

  Arjan> fair enough; I hope this means the next generation has this
  Arjan> wart fixed...
  >>  I wouldn't hold my breath.  My impression was that the Intel
  >> chipset folks don't want I/O MMU because (a) Windows doesn't need
  >> it and (b) real machines use (close-to-)64-bit-capable hardware.

  Bill> Doesn't need it? Does that mean the Win64 uses bounce buffers
  Bill> for everything? Or am I totally misreading this?

Remember: I'm just the messenger here...

I have no idea what Win64 does, but obviously bounce buffering is only
an issue for devices that can't address all physical memory.  These
days, even relatively low-end machines have devices that can address
"more than enough" physical memory (I'm not sure exactly what the DMA
limit of, say, a Kenai32 e1000 card is, but it's a lot more than 4GB).

	--david

  reply	other threads:[~2004-02-20  4:03 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         ` [PATCH] Intel x86-64 support merge Bill Davidsen
2004-02-20  4:03           ` David Mosberger-Tang [this message]
2004-02-20  4:19           ` Jeff Garzik
2004-02-20  7:48             ` Jes Sorensen
2004-02-21  2:07               ` David Mosberger
     [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=16437.34558.298388.89482@panda.mostang.com \
    --to=davidm@mostang.com \
    --cc=David.Mosberger@acm.org \
    --cc=davidsen@tmr.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