Again re-sending due to messed-up quoting: On 17 Oct 2022, at 22:44, Harry Butterworth <heb1...@gmail.com<mailto:heb1...@gmail.com>> wrote:
> On Sun, 16 Oct 2022 at 14:09, Lucy Parker > <lucy.par...@student.unsw.edu.au<mailto:lucy.par...@student.unsw.edu.au>> > wrote: > > >> We propose adding a second hw thread, one to service each direction… >> > This is entirely plausible. > > Be aware: the threads won’t be independent. For example, ACKs or timing > information coming in on the receive thread will need to be communicated to > the sending thread. I think you’re talking about IP-level issues. These aren’t the driver’s business, which is solely concerned with hardware abstraction. And yes, the IP stack won’t be able to keep transmit and receive streams separate. But the IP stack will be per-client and not isolation-critical (and not introducing new complications AFAICT). Gernot _______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems _______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems
