Pete Zaitcev wrote :
>
> Do you realize that "block" means "enterering the kernel and calling
> schedule()", which is exactly what is NOT happening in the patch?
> I would not mind if the tools "blocked in GIWSCAN", only until
> it returns success and not EGAIN.
Do you realise that "block" means holding the netlink
mutex. Which means any networking ioctl and netlink operation is
blocked, which means ifconfig and iproute are blocked.
The MadWifi driver take up to 15sec to perfom scanning.
> With EAGAIN returned, you have to a) block elsewhere and not in
> GIWSCAN (perhaps in sleep(2) or select(2)), or b) not block at all
> and loop.
User-space authors are no dummy, they know that looping on
EAGAIN is bad, so most do a sleep (actually most user-space use libiw
which does a sleep).
> It is correct, no doubt. The discussion is about wether it is
> desirable.
Yes, it is desirable, because we are pragmatic.
Jean
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
