netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Christoph Lameter <clameter@sgi.com>,
	Andrew Morton <akpm@osdl.org>, linux-netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH] Optimize loopback stats
Date: Tue, 15 Mar 2005 16:09:43 -0800	[thread overview]
Message-ID: <42377947.5090207@us.ibm.com> (raw)
In-Reply-To: <200503151819_MC3-1-98A4-43AC@compuserve.com>

Chuck Ebbert wrote:

> On 15-Mar-05 Nivedita Singhvi wrote:
> 
> 
>>Chuck Ebbert wrote:
>>
>>
>>>  This patch optimizes the loopback driver's statistics by using a single
>>>counter for rx and tx stats instead of one for rx and one for tx.  It also
>>>adds unlikely() to the test for TSO since it's no longer supported by default.
>>>(Maybe the TSO code should be bracketed by "#if 0" ?)
>>
>>Hmm, some of us want those counters separate - if this is really
>>needed, could it be a configurable option, please?
> 
> 
>  But they _are_ separately reported -- get_stats() takes care of that.
> Everything looks exactly the same to userspace after this patch.
> 
> 
> 
> 
> --
> Chuck
> 
Hmm, I see the following in your patch:

+               stats->rx_bytes   += lb_stats->rx_tx_bytes;
+               stats->tx_bytes    = stats->rx_bytes;

Doesn't that mean RX is now twice what it should be
and so is TX? They are separately reported, but if
so, their real value should be half of rx_tx_bytes
each, correct?

thanks,
Nivedita

  reply	other threads:[~2005-03-16  0:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 23:15 [PATCH] Optimize loopback stats Chuck Ebbert
2005-03-16  0:09 ` Nivedita Singhvi [this message]
2005-03-16  0:18   ` Nivedita Singhvi
  -- strict thread matches above, loose matches on Subject: below --
2005-03-15 19:56 Chuck Ebbert
2005-03-15 20:14 ` Nivedita Singhvi
2005-03-15 20:49   ` Nivedita Singhvi

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=42377947.5090207@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=netdev@oss.sgi.com \
    /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).