From: "David S. Miller" <davem@davemloft.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: netdev@oss.sgi.com
Subject: Re: netdev ioctl & dev_base_lock : bad idea ?
Date: Thu, 9 Dec 2004 15:19:08 -0800 [thread overview]
Message-ID: <20041209151908.7f84eaf6.davem@davemloft.net> (raw)
In-Reply-To: <1102630475.22746.7.camel@gaston>
On Fri, 10 Dec 2004 09:14:35 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> Also, why would we need the xmit lock when calling netif_wake_queue() ?
> I'm not sure I get that one (but I'm not too familiar with the net core
> neither).
Hmmm, you're right, it seems it is not needed.
prev parent reply other threads:[~2004-12-09 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 8:48 netdev ioctl & dev_base_lock : bad idea ? Benjamin Herrenschmidt
2004-12-09 6:06 ` David S. Miller
2004-12-09 6:22 ` Benjamin Herrenschmidt
2004-12-09 7:13 ` David S. Miller
2004-12-09 22:14 ` Benjamin Herrenschmidt
2004-12-09 23:19 ` David S. Miller [this message]
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=20041209151908.7f84eaf6.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--cc=netdev@oss.sgi.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).