From: Stephen Hemminger <shemminger@osdl.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] e1000: Real time packets and bytes statistics
Date: Thu, 12 Oct 2006 14:29:43 -0700 [thread overview]
Message-ID: <20061012142943.2a93893e@freekitty> (raw)
In-Reply-To: <20061012230252.8b5a1ebb.khali@linux-fr.org>
On Thu, 12 Oct 2006 23:02:52 +0200
Jean Delvare <khali@linux-fr.org> wrote:
> Hi Stephen,
>
> On 10/11/06, Stephen Hemminger wrote:
> > On Wed, 11 Oct 2006, Jesse Brandeburg wrote:
> > > On 10/11/06, Jean Delvare wrote:
> > > > Let the e1000 driver report the most important statistics (rx/tx_bytes
> > > > and rx/tx_packets) in real time, rather than every other second. This
> > > > is similar to what the e100 driver is doing.
> > > > (...)
> > > > --- linux-2.6.19-rc1.orig/drivers/net/e1000/e1000_main.c 2006-10-11 10:53:49.000000000 +0200
> > > > +++ linux-2.6.19-rc1/drivers/net/e1000/e1000_main.c 2006-10-11 11:34:41.000000000 +0200
> > > > @@ -3118,6 +3118,8 @@
> > > > e1000_tx_map(adapter, tx_ring, skb, first,
> > > > max_per_txd, nr_frags, mss));
> > > >
> > > > + adapter->net_stats.tx_packets++;
> > > > + adapter->net_stats.tx_bytes += skb->len;
> > > > netdev->trans_start = jiffies;
> > >
> > > this is the part I'm most worried about. as I believe it to be
> > > incorrect for TSO packets. Maybe something like?
> > > + if (skb_shinfo(skb)->gso_segs)
> > > + adapter->net_stats.tx_packets += skb_shinfo(skb)->gso_segs;
> > > + else
> > > + adapter->net_stats.tx_packets++;
> > > + adapter->net_stats.tx_bytes += skb->len;
> > > netdev->trans_start = jiffies;
> > >
> > > skb len will still be off by some amount, because the skb->data
> > > (header) is replicated across each gso segment but only counted once
> > > this way, but hopefully someone will pipe up with a good way to
> > > compute that.
> >
> > You might want to put the tx values in a per-cpu structure and
> > sum later. Incrementing statistics can actually be a performance
> > bottleneck on SMP tests, because it causes lots of cache thrashing.
>
> I don't really see how this would be implemented. Can you please point
> me to other drivers which do it that way?
>
> Thanks,
Loopback (drivers/net/loopback.c) does it, but it is simpler since it doesn't
have to support multiple interfaces. In a normal driver you would have to use
indirection and alloc_percpu() like af_inet.c does.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-10-12 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 11:35 [PATCH] e1000: Real time packets and bytes statistics Jean Delvare
2006-10-11 17:44 ` Jesse Brandeburg
2006-10-12 17:30 ` Stephen Hemminger
2006-10-12 21:02 ` Jean Delvare
2006-10-12 21:29 ` Stephen Hemminger [this message]
2006-10-12 21:20 ` Jean Delvare
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=20061012142943.2a93893e@freekitty \
--to=shemminger@osdl.org \
--cc=jesse.brandeburg@gmail.com \
--cc=khali@linux-fr.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.