Re: Changes in the network interface queueing handoff model



On 31-Jul-2006 Petri Helenius wrote:
Robert Watson wrote:

I tend to agree, but implemented full queueing support for if_em to
make sure I understood to complexity implications of completely
removing queueing from the ifnet side dispatch. I guess an
interesting question for us is how we decide what the right threshold
is to implement software queuing. Do any if_em cards need software
queueing, or do they all have adequate in-hardware queues as is?
Entirely cutting the queue code would significantly simplify
em_startmbuf.
Actually most em cards support 4096 descriptors each way.

Yes, even the earliest ones supported 4096 descriptors on paper. In
practice, the early chips had bugs that required the entire descriptor
ring to fit in a single page of memory. That limited them to 4096/16
= 256 transmit descriptors on x86 hardware at the time. That chip
bug was fixed a long time ago, though, and in any case 256 transmit
descriptors is a lot for most applications.

John
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Changes in the network interface queueing handoff model
    ... but implemented full queueing support for if_em to ... Actually most em cards support 4096 descriptors each way. ... even the earliest ones supported 4096 descriptors on paper. ... = 256 transmit descriptors on x86 hardware at the time. ...
    (freebsd-net)
  • [PATCH 19/19] iop3xx: IOP 32x and 33x support for the iop-adma driver
    ... Adds the platform device definitions and the architecture specific support ... fix places where software descriptors are assumed to be contiguous, ... iop32x does not support hardware zero sum, ... new file mode 100644 ...
    (Linux-Kernel)
  • Re: USBSER.SYS: where to get a bug-free version?
    ... Windows does support composite devices. ... Also, as far as I am aware, Windows does not support DFU as a class and USB ... > following additional descriptors are inserted within each run-time ...
    (microsoft.public.development.device.drivers)
  • Re: USBSER.SYS: where to get a bug-free version?
    ... to support is one thing, but producing BSOD's because of not supporting is another. ... DFU specs (chapt. ... following additional descriptors are inserted within each run-time ... Run-Time Device and Configuration Descriptors ...
    (microsoft.public.development.device.drivers)
  • Re: [PATCH] SATA NCQ support
    ... so this is for AHCI. ... NCQ requires hardware support from both the controller and hard drive, ... Legacy queueing doesn't require support in the controller, ...
    (Linux-Kernel)