Ethernet Bridge development
 help / color / mirror / Atom feed
From: Jaime Medrano <jaime.medrano@gmail.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Getting statistics from a bridge
Date: Thu, 24 Apr 2008 15:41:29 +0200	[thread overview]
Message-ID: <20080424134129.GA27496@localhost> (raw)
In-Reply-To: <20080423104340.2416280e@extreme>

On Wed, Apr 23, 2008 at 10:43:40AM -0700, Stephen Hemminger wrote:
> On Wed, 23 Apr 2008 10:53:12 +1000
> "Leigh Sharpe" <lsharpe@pacificwireless.com.au> wrote:
> 
> >  Is there any way of getting detailed statistics from a bridge?
> > Specifically, I need to know how many frames may have been dropped
> > because they exceed the MTU of the underlying port. I'm having a few
> > issues with MTUs not agreeing.
> 
> It would not be hard to modify kernel to use one of the existing statistics on
> the bridge interface to keep track of the dropped packets. I'll look into it
> if no one else gets to it first (hint, hint)
> 

I think this change will do it.

Regards,
Jaime Medrano.

--- linux-2.6.25.orig/net/bridge/br_forward.c	2008-04-24 11:04:32.000000000 +0200
+++ linux-2.6.25/net/bridge/br_forward.c	2008-04-24 15:15:02.000000000 +0200
@@ -35,9 +35,10 @@
 int br_dev_queue_push_xmit(struct sk_buff *skb)
 {
 	/* drop mtu oversized packets except gso */
-	if (packet_length(skb) > skb->dev->mtu && !skb_is_gso(skb))
+	if (packet_length(skb) > skb->dev->mtu && !skb_is_gso(skb)) {
+		rcu_dereference(skb->dev->br_port)->br->statistics.tx_dropped++;
 		kfree_skb(skb);
-	else {
+	} else {
 		/* ip_refrag calls ip_fragment, doesn't copy the MAC header. */
 		if (nf_bridge_maybe_copy_header(skb))
 			kfree_skb(skb);

  reply	other threads:[~2008-04-24 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  0:53 [Bridge] Getting statistics from a bridge Leigh Sharpe
2008-04-23 17:43 ` Stephen Hemminger
2008-04-24 13:41   ` Jaime Medrano [this message]
2008-04-28 18:10     ` Stephen Hemminger

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=20080424134129.GA27496@localhost \
    --to=jaime.medrano@gmail.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=shemminger@linux-foundation.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