From: Jean Tourrilhes <jt@hpl.hp.com>
To: Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org, Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: [patch 1/3] softmac: return -EAGAIN from getscan while scanning
Date: Thu, 13 Apr 2006 16:58:03 -0700 [thread overview]
Message-ID: <20060413235803.GA23116@bougret.hpl.hp.com> (raw)
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
next reply other threads:[~2006-04-13 23:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 23:58 Jean Tourrilhes [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-14 0:01 [patch 1/3] softmac: return -EAGAIN from getscan while scanning Jean Tourrilhes
2006-04-14 15:58 ` Herbert Xu
[not found] <20060411085805.949313000@sipsolutions.net>
[not found] ` <20060411085841.252064000@sipsolutions.net>
2006-04-13 9:00 ` Pete Zaitcev
2006-04-13 9:06 ` Johannes Berg
2006-04-13 9:34 ` Johannes Berg
2006-04-13 12:14 ` Dan Williams
2006-04-13 16:13 ` Jean Tourrilhes
2006-04-15 19:24 ` Johannes Berg
2006-04-15 21:27 ` Dan Williams
2006-04-13 12:12 ` Dan Williams
2006-04-13 12:19 ` Johannes Berg
2006-04-13 16:00 ` Jouni Malinen
2006-04-13 22:28 ` Pete Zaitcev
2006-04-13 22:45 ` Jouni Malinen
2006-04-13 23:03 ` Stephen Hemminger
2006-04-13 23:35 ` Pete Zaitcev
2006-04-13 22:21 ` Pete Zaitcev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060413235803.GA23116@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=zaitcev@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).