* wireless: NETDEV_TX_LOCKED, use it or not?
@ 2006-08-19 10:22 Michael Buesch
0 siblings, 0 replies; only message in thread
From: Michael Buesch @ 2006-08-19 10:22 UTC (permalink / raw)
To: netdev; +Cc: bcm43xx-dev
Hi,
I am currently wondering, if we should use NETDEV_TX_LOCKED
in the bcm43xx wireless net driver.
I currently don't have an SMP machine with a bcm43xx card
running, so I can't use benchmarks to find out.
There are various things to consider:
* The RX and TX-status paths, which also must take the spinlock
aren't more expensive than on a normal Ethernet card (at least
with d80211 stack).
* But the retry-path, when a NETDEV_TX_LOCKED is returned is
slightly more expensive.
Well, the question is: Is it worth to return NETDEV_TX_LOCKED
on spinlock contention, or is it better to spin?
Is NETDEV_TX_LOCKED only desired on gigabit ethernet?
Thanks.
--
Greetings Michael.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-08-19 10:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-19 10:22 wireless: NETDEV_TX_LOCKED, use it or not? Michael Buesch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).