| To: | Noah Romer <nromer@xxxxxxxx> |
|---|---|
| Subject: | Re: hard_start_xmit behavior |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 16 Jul 2001 15:30:21 -0700 (PDT) |
| Cc: | netdev <netdev@xxxxxxxxxxx>, "Romer, Noah" <noah.romer@xxxxxxxx> |
| In-reply-to: | <3B5355AB.C5D62090@xxxxxxxx> |
| References: | <3B5355AB.C5D62090@xxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
Noah Romer writes: > Specifically, if the network stack gives you a packet to transmit and you > immediately know you're not going to be able to do so (in my case, when I'm > unable to get a message frame so I can talk with the board, a rare > condition), > what's the expected handling of the skb and what does the network stack want > to > see as the return value? If you cannot queue the packet then: netif_stop_queue(dev); return 1; And do nothing else. Later, David S. Miller davem@xxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: hard_start_xmit behavior, Noah Romer |
|---|---|
| Next by Date: | Re: [PATCH] skb_{over,under}_panic optimizations, David S. Miller |
| Previous by Thread: | Re: hard_start_xmit behavior, Noah Romer |
| Next by Thread: | illegal source address & source address selection, Moter Du |
| Indexes: | [Date] [Thread] [Top] [All Lists] |