Crossbow doesn't change that. It virtualizes the tx/rx rings management and queries the h/w capability from the driver.
The bge driver currently sets an upper rx/tx limit and changes that thereafter for each specific driver. We can see a large diversity among bcm57xx chipsets. On Wed, 2008-05-07 at 14:09 +0800, Darren Reed wrote: > Crisson Hu wrote: > > I checked the tx/rx ring number of BCM5721 from the docs, it says the ring > > number is one. From the link[1], it discussed several chipsets whose rx/tx > > rings are possibly set to four, but we have to try it. > > > > >From the code side, bge_attach will set the tx_ring/rx_ring to that from > > >bge.conf, then calls bge_chip_id_init to reset the tx_ring/rx_ring of > > >BCM5721 to BGE_SEND_RINGS_MAX_5705/BGE_RECV_RINGS_MAX_5705 (which is > > >defined as one). This means you possibly need to change the code for that. > > > > It seems like a bug to define the maximum number of rings > with a constant. Do you know if crossbow fixes or changes > this? > > Darren > -- ************************************* * Guang-Hao, Crisson Hu * * China ERI, Sun Microsystems, Inc. * * Tel: +86-10-62673095 * ************************************* _______________________________________________ networking-discuss mailing list [email protected]
