All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Zhang <zhangseven@gmail.com>
To: bridge@lists.osdl.org
Subject: [BRIDGE]A basic question: what's the relationship of the Rx/Tx packets count between the bridge and its enslaved NIC.
Date: Tue, 16 Aug 2005 11:40:40 +0800	[thread overview]
Message-ID: <fd54385205081520403350f16a@mail.gmail.com> (raw)

I have a bridge br0, it enslaves two NICs: eth0 and eth1. 
By using "cat /proc/net/dev ", i can see the Rx/Tx packets and bytes
through each interface. just like this:

[* time tick 1 *]

Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed
multicast|bytes    packets errs drop fifo colls carrier compressed
    lo: 3926521   14121    0    0    0     0          0         0 
3926521   14121    0    0    0     0       0          0
  eth0: 7255431   37878    0    0    0     0          0         0
12869195   26229    0    0    0     0       0          0
  eth1:12172910   25800    3    3    0     3          0         0 
7849528   38567   72    0    0     5      77          0
   br0: 3035036   17478    0    0    0     0          0         0 
2950728   12908    0    0    0     0       0          0
 
[* time tick 2 *]

Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed
multicast|bytes    packets errs drop fifo colls carrier compressed
    lo: 4020580   14734    0    0    0     0          0         0 
4020580   14734    0    0    0     0       0          0
  eth0: 7780868   41663    0    0    0     0          0         0
17450012   30518    0    0    0     0       0          0
  eth1:16759363   30073    3    3    0     3          0         0 
8375862   42391   72    0    0     5      77          0
   br0: 3086377   17819    0    0    0     0          0         0 
2986052   13185    0    0    0     0       0          0

[* the delta value *]

Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed
multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:   94059     613    0    0    0     0          0         0   
94059     613    0    0    0     0       0          0
  eth0:  525437    3785    0    0    0     0          0         0 
4580817    4289    0    0    0     0       0          0
  eth1: 4586453    4273    0    0    0     0          0         0  
526334    3824    0    0    0     0       0          0
   br0:   51341     341    0    0    0     0          0         0   
35324     277    0    0    0     0       0          0

I wonder the meaning of the value of the br0,  it's Rx/Tx packets is
less than both eth0 and eth1.
what's the relationship of the values between bridge and it's enslaved NIC?

Thanks for your comments on this.


             reply	other threads:[~2005-08-16  3:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  3:40 Steven Zhang [this message]
2005-08-17 16:21 ` [BRIDGE]A basic question: what's the relationship of the Rx/Tx packets count between the bridge and its enslaved NIC Stephen Hemminger
2005-08-22  9:25   ` Zoran s
2005-08-22  9:34   ` Zoran s

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=fd54385205081520403350f16a@mail.gmail.com \
    --to=zhangseven@gmail.com \
    --cc=bridge@lists.osdl.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.