From: "David S. Miller" <davem@davemloft.net>
To: ralf@linux-mips.org
Cc: alan@lxorguk.ukuu.org.uk, netdev@oss.sgi.com
Subject: Re: Strange uses of netif_start_queue
Date: Fri, 12 Aug 2005 11:03:20 -0700 (PDT) [thread overview]
Message-ID: <20050812.110320.97292810.davem@davemloft.net> (raw)
In-Reply-To: <20050812133905.GF2819@linux-mips.org>
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 12 Aug 2005 14:39:05 +0100
> To answer the fundamental question, I think netif_start_queue /
> netif_stop_queue should be allowed in case the driver for some reason has
> the desire to stop queueing of packet immediately after register_netdev.
I disagree. register_netdev() does not make packets start getting
queued, you have to up the interface for that to start occuring.
And your ->open() routine has full control over that.
next prev parent reply other threads:[~2005-08-12 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 13:35 Strange uses of netif_start_queue Alan Cox
2005-08-12 13:27 ` Ralf Baechle
2005-08-12 13:39 ` Ralf Baechle
2005-08-12 18:03 ` David S. Miller [this message]
2005-08-12 13:33 ` Patrick McHardy
2005-08-12 18:00 ` David S. Miller
2005-08-12 18:46 ` Thomas Graf
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=20050812.110320.97292810.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=netdev@oss.sgi.com \
--cc=ralf@linux-mips.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).