| To: | Matt Mackall <mpm@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [patch] tg3 ring buffer allocation error handling |
| From: | Sven Schuster <schuster.sven@xxxxxx> |
| Date: | Wed, 14 Apr 2004 22:59:59 +0200 |
| Cc: | Jeff Garzik <jgarzik@xxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040414184642.GZ1175@xxxxxxxxx> |
| References: | <20040414184642.GZ1175@xxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.6i |
On Wed, Apr 14, 2004 at 01:46:42PM -0500, Matt Mackall told us:
> if (tp->tg3_flags & TG3_FLAG_JUMBO_ENABLE) {
> for (i = 0; i < tp->rx_jumbo_pending; i++) {
> if (tg3_alloc_rx_skb(tp, RXD_OPAQUE_RING_JUMBO,
> - -1, i) < 0)
> - break;
> + -1, i) < 0) {
> + printk("tg3_alloc_rx_skb %d failed\n", i);
> + return -ENOMEM;
Please correct me if I'm wrong, but shouldn't the buffers from the
irst allocation (RXD_OPAQUE_RING_STD) be freed (maybe via
tg3_free_rings??) when we get an error here??
Sven
> + }
> }
> }
> +
> + return 0;
> }
>
--
Linux zion 2.6.5 #1 Sun Apr 4 19:56:55 CEST 2004 i686 athlon i386 GNU/Linux
22:53:42 up 9 days, 23:37, 2 users, load average: 0.00, 0.00, 0.00
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 2.6.5] bridge - replace CLEAR_BITMAP with memset, Stephen Hemminger |
|---|---|
| Next by Date: | Re: [Fwd: extra spinlocking in forcedeth 0.25], Andrew de Quincey |
| Previous by Thread: | [patch] tg3 ring buffer allocation error handling, Matt Mackall |
| Next by Thread: | Re: [patch] tg3 ring buffer allocation error handling, Matt Mackall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |