From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org, Bcm43xx-dev@lists.berlios.de
Subject: Re: Please pull 'bcm43xx' branch of wireless-2.6?
Date: Mon, 31 Jul 2006 16:01:43 -0400 [thread overview]
Message-ID: <44CE61A7.4010207@garzik.org> (raw)
In-Reply-To: <20060731191014.GD10138@tuxdriver.com>
John W. Linville wrote:
> Jeff, if a 10ms maximum delay is still acceptable to you, then please
> pull from the bcm43xx branch of wireless-2.6 into the upstream branch
> of netdev-2.6.
Just to be clear, 'upstream' not 'upstream-fixes', correct?
> P.S. FWIW, I'm still not totally happy w/ the (potential for a)
> long busy wait. But, this series of patches makes things better by
> 100x over what is currently in the tree. So, it seems worthwhile.
> I'll keep further reductions as an item on my TODO list, FWIW... :-)
Agreed. And there are some existing busy-waits that (1) _obviously_
need to be converted to mdelay(), and (2) eventually need to be
converted to msleep().
Overall, the Linux kernel community consensus is that long synchronous
delays spinning the CPU should be avoided.
Jeff
next prev parent reply other threads:[~2006-07-31 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 0:22 Please pull 'upstream-fixes' branch of wireless-2.6 John W. Linville
2006-07-28 0:23 ` Please pull 'upstream' " John W. Linville
[not found] ` <20060728002358.GB11621-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2006-07-28 0:37 ` What's new in 'bcm43xx' branch of wireless-2.6? John W. Linville
[not found] ` <20060728003753.GC11621-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2006-07-31 19:10 ` Please pull " John W. Linville
2006-07-31 20:01 ` Jeff Garzik [this message]
[not found] ` <44CE61A7.4010207-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2006-07-31 20:04 ` John W. Linville
2006-08-03 21:21 ` Jeff Garzik
2006-07-29 4:33 ` Please pull 'upstream' branch of wireless-2.6 Jeff Garzik
2006-07-29 4:32 ` Please pull 'upstream-fixes' " Jeff Garzik
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=44CE61A7.4010207@garzik.org \
--to=jeff@garzik.org \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).