Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Newsgroups | comp.arch |
| Subject | Re: DMA is obsolete |
| Date | 2025-05-01 13:07 +0000 |
| Organization | PANIX Public Access Internet and UNIX, NYC |
| Message-ID | <vuvrlr$att$1@reader1.panix.com> (permalink) |
| References | <vuj131$fnu$1@gal.iecc.com> <CJ8PP.2629170$eNx6.1327988@fx14.iad> <da5b3dea460370fc1fe8ad2323da9bc4@www.novabbs.org> |
In article <da5b3dea460370fc1fe8ad2323da9bc4@www.novabbs.org>, MitchAlsup1 <mitchalsup@aol.com> wrote: >On Sat, 26 Apr 2025 17:29:06 +0000, Scott Lurndal wrote: >[snip] >Reminds me of trying to sell a micro x86-64 to AMD as a project. >The ยต86 is a small x86-64 core made available as IP in Verilog >where it has/runs the same ISA as main GBOoO x86, but is placed >"out in the PCIe" interconnect--performing I/O services topo- >logically adjacent to the device itself. This allows 1ns access >latencies to DCRs and performing OS queueing of DPCs,... without >bothering the GBOoO cores. > >AMD didn't buy the arguments. I can see it either way; I suppose the argument as to whether I buy it or not comes down to, "in depends". How much control do I, as the OS implementer, have over this core? If it is yet another hidden core embedded somewhere deep in the SoC complex and I can't easily interact with it from the OS, then no thanks: we've got enough of those between MP0, MP1, MP5, etc, etc. On the other hand, if it's got a "normal" APIC ID, the OS has control over it like any other LP, and its coherent with the big cores, then yeah, sign me up: I've been wanting something like that for a long time now. Consider a virtualization application. A problem with, say, SR-IOV is that very often the hypervisor wants to interpose some sort of administrative policy between the virtual function and whatever it actually corresponds to, but get out of the fast path for most IO. This implies a kind of offload architecture where there's some (presumably software) agent dedicated to handling IO that can be parameterized with such a policy. A core very close to the device could handle that swimmingly, though I'm not sure it would be enough to do it at (say) line rate for a 400Gbps NIC or Gen5 NVMe device. ...but why x86_64? It strikes me that as long as the _data_ formats vis the software-visible ABI are the same, it doesn't need to use the same ISA. In fact, I can see advantages to not doing so. - Dan C.
Back to comp.arch | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
DMA is obsolete John Levine <johnl@taugh.com> - 2025-04-26 16:19 +0000
Re: DMA is obsolete Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-04-26 16:28 +0000
Re: DMA is obsolete Terje Mathisen <terje.mathisen@tmsw.no> - 2025-04-26 19:28 +0200
Re: DMA is obsolete Theo <theom+news@chiark.greenend.org.uk> - 2025-04-27 19:35 +0100
Re: DMA is obsolete mitchalsup@aol.com (MitchAlsup1) - 2025-04-27 20:49 +0000
Re: DMA is obsolete scott@slp53.sl.home (Scott Lurndal) - 2025-04-27 22:37 +0000
Re: DMA is obsolete Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-28 01:20 +0000
Re: DMA is obsolete scott@slp53.sl.home (Scott Lurndal) - 2025-04-26 17:29 +0000
Re: DMA is obsolete mitchalsup@aol.com (MitchAlsup1) - 2025-04-26 19:25 +0000
Re: DMA is obsolete scott@slp53.sl.home (Scott Lurndal) - 2025-04-27 14:01 +0000
Re: DMA is obsolete scott@slp53.sl.home (Scott Lurndal) - 2025-04-27 16:12 +0000
Re: DMA is obsolete scott@slp53.sl.home (Scott Lurndal) - 2025-04-27 14:02 +0000
Re: DMA is obsolete Theo <theom+news@chiark.greenend.org.uk> - 2025-04-27 20:13 +0100
Re: DMA is obsolete mitchalsup@aol.com (MitchAlsup1) - 2025-04-27 20:45 +0000
Re: DMA is obsolete scott@slp53.sl.home (Scott Lurndal) - 2025-04-27 22:44 +0000
Re: DMA is obsolete cross@spitfire.i.gajendra.net (Dan Cross) - 2025-05-01 13:07 +0000
Re: DMA is obsolete mitchalsup@aol.com (MitchAlsup1) - 2025-05-01 22:03 +0000
Re: DMA is obsolete cross@spitfire.i.gajendra.net (Dan Cross) - 2025-05-02 02:15 +0000
Re: DMA is obsolete anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-05-02 05:34 +0000
Re: DMA is obsolete cross@spitfire.i.gajendra.net (Dan Cross) - 2025-05-02 15:02 +0000
Re: DMA is obsolete anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2025-05-03 06:11 +0000
Re: DMA is obsolete Robert Finch <robfi680@gmail.com> - 2025-05-03 06:32 -0400
Re: DMA is obsolete cross@spitfire.i.gajendra.net (Dan Cross) - 2025-05-03 13:33 +0000
IP (was: DMA is obsolete) Stefan Monnier <monnier@iro.umontreal.ca> - 2025-05-03 10:50 -0400
Re: IP (was: DMA is obsolete) Thomas Koenig <tkoenig@netcologne.de> - 2025-05-03 15:15 +0000
Re: IP (was: DMA is obsolete) John Levine <johnl@taugh.com> - 2025-05-03 15:46 +0000
Re: IP (was: DMA is obsolete) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-05-03 16:52 +0000
Re: IP (was: DMA is obsolete) scott@slp53.sl.home (Scott Lurndal) - 2025-05-03 21:31 +0000
Re: IP Stefan Monnier <monnier@iro.umontreal.ca> - 2025-05-03 23:04 -0400
Re: IP cross@spitfire.i.gajendra.net (Dan Cross) - 2025-05-04 09:56 +0000
Re: IP Thomas Koenig <tkoenig@netcologne.de> - 2025-05-04 10:17 +0000
Re: IP mitchalsup@aol.com (MitchAlsup1) - 2025-05-04 18:16 +0000
Re: IP Bill Findlay <findlaybill@blueyonder.co.uk> - 2025-05-04 19:37 +0100
Re: IP Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-05-04 21:31 +0000
Re: DMA is obsolete Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-05-04 06:44 +0000
Re: DMA is obsolete scott@slp53.sl.home (Scott Lurndal) - 2025-05-03 21:53 +0000
Re: DMA is obsolete mitchalsup@aol.com (MitchAlsup1) - 2025-05-03 23:02 +0000
Re: DMA is obsolete cross@spitfire.i.gajendra.net (Dan Cross) - 2025-05-21 12:36 +0000
Re: DMA is obsolete mitchalsup@aol.com (MitchAlsup1) - 2025-05-02 17:40 +0000
Re: DMA is obsolete Terje Mathisen <terje.mathisen@tmsw.no> - 2025-05-03 14:29 +0200
ND-10 (was Re: DMA is obsolete) Lars Poulsen <lars@beagle-ears.com> - 2025-05-03 23:30 +0000
Re: ND-10 (was Re: DMA is obsolete) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-05-04 02:10 +0000
csiph-web