From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
dahinds@users.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 3c589_cs: don't reference skb after passing it to netif_rx
Date: Mon, 26 Feb 2001 21:26:51 -0300 [thread overview]
Message-ID: <20010226212651.Q8692@conectiva.com.br> (raw)
In-Reply-To: <20010226211058.M8692@conectiva.com.br> <3A9B0936.17170236@mandrakesoft.com>
In-Reply-To: <3A9B0936.17170236@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Mon, Feb 26, 2001 at 08:56:06PM -0500
Em Mon, Feb 26, 2001 at 08:56:06PM -0500, Jeff Garzik escreveu:
> Arnaldo Carvalho de Melo wrote:
> > --- linux-2.4.2/drivers/net/pcmcia/3c589_cs.c Tue Feb 13 19:15:05 2001
> > +++ linux-2.4.2.acme/drivers/net/pcmcia/3c589_cs.c Mon Feb 26 22:44:00 2001
> > @@ -992,9 +992,9 @@
> > (pkt_len+3)>>2);
> > skb->protocol = eth_type_trans(skb, dev);
> >
> > + lp->stats.rx_bytes += skb->len;
> > netif_rx(skb);
> > lp->stats.rx_packets++;
> > - lp->stats.rx_bytes += skb->len;
>
> I prefer the attached patch instead. It makes use of the existing local
> 'pkt_len', and it checks off another item that should probably be on the
> janitor's todo list: Set 'dev->last_rx=jiffies' immediately after
> netif_rx.
Thanks, I've added your comments and Donald one about grouping the stat
updates, as always the Janitor's TODO list is available at
http://bazar.conectiva.com.br/~acme/TODO, so get your broom and keep on
cleaning 8)
- Arnaldo
next prev parent reply other threads:[~2001-02-27 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 0:10 [PATCH] 3c589_cs: don't reference skb after passing it to netif_rx Arnaldo Carvalho de Melo
2001-02-27 1:56 ` Jeff Garzik
2001-02-27 0:26 ` Arnaldo Carvalho de Melo [this message]
2001-02-27 2:07 ` Jeff Garzik
2001-02-27 0:32 ` Arnaldo Carvalho de Melo
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=20010226212651.Q8692@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dahinds@users.sourceforge.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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).