| To: | ralf@xxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Strange uses of netif_start_queue |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Fri, 12 Aug 2005 11:03:20 -0700 (PDT) |
| Cc: | alan@xxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20050812133905.GF2819@linux-mips.org> |
| References: | <1123853714.22460.39.camel@localhost.localdomain> <20050812132758.GE2819@linux-mips.org> <20050812133905.GF2819@linux-mips.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Ralf Baechle <ralf@xxxxxxxxxxxxxx> 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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Strange uses of netif_start_queue, David S. Miller |
|---|---|
| Next by Date: | Re: Strange uses of netif_start_queue, Thomas Graf |
| Previous by Thread: | Re: Strange uses of netif_start_queue, Ralf Baechle |
| Next by Thread: | Re: Strange uses of netif_start_queue, Patrick McHardy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |