Intel x86-64 support merge
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · David Mosberger-Tang
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Arjan van de Ven
Quoted 2 lines · H. Peter Anvin
Quoted 2 lines
Because they were caught by surprise and just hacked the chips
they had in the pipeline, presumably.
Quoted 6 lines
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.
Doesn't need it? Does that mean the Win64 uses bounce buffers for everything? Or am I totally misreading this?
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Bill Davidsen
Quoted 3 lines · Bill> David Mosberger-Tang wrote:
Quoted 3 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
On Thu, 19 Feb 2004 00:40:24 +0100, Arjan van de Ven <[email protected]> said:
Quoted 2 lines · H. Peter Anvin
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
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...
Quoted 3 lines
Quoted 3 lines
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
Quoted 13 lines · Bill Davidsen
Quoted 11 lines · David Mosberger-Tang
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Arjan van de Ven
Quoted 2 lines · H. Peter Anvin
Quoted 2 lines
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...
Quoted 6 lines
Quoted 3 lines
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.
Doesn't need it? Does that mean the Win64 uses bounce buffers for everything? Or am I totally misreading this?
Well, for 32-bit PCI hardware on a 64-bit OS, you pretty much have to bounce, without an IOMMU.
I doubt Win64 bounces for 64-bit PCI hardware, but who knows...
Jeff
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Jeff" == Jeff Garzik <[email protected]> writes:
Quoted 2 lines · Jeff> Bill Davidsen wrote:
Quoted 2 lines
Doesn't need it? Does that mean the Win64 uses bounce buffers for everything? Or am I totally misreading this?
Jeff> Well, for 32-bit PCI hardware on a 64-bit OS, you pretty much Jeff> have to bounce, without an IOMMU.
Jeff> I doubt Win64 bounces for 64-bit PCI hardware, but who knows...
Just a shame they don't seem to care about performance and allowing one to issue SAC cycles when possible. Oh well, guess one just has to buy a real computer.
Cheers,
Jes
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Jes Sorensen
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