All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Drukker <vlad@storewiz.com>
To: Stephen Hemminger <shemminger@osdl.org>,
	";Henrik Nordstrom" <hno@marasystems.com>,
	";David S. Miller" <davem@davemloft.net>
Cc: bridge@osdl.org
Subject: [Bridge] Re: [PATCH] TSO fix in br_dev_queue_push_xmit
Date: Wed, 21 Sep 2005 15:53:06 +0300	[thread overview]
Message-ID: <1127307186.15678.63.camel@quant> (raw)
In-Reply-To: <20050921.001427.27575173.davem@davemloft.net>

Hi,

I see you all agree to apply :)

Stephen, repost of this patch to proper places below.

Thank you Henrik for clarification of bridge standard.
However, silent drop of locally generated packets on 99% idle carrier
grade machine looks like a hardware problem.

David, don't you think that having software packet drop counters is a
bad idea? I thought, software drop counters are there to help identify
hardware problems or lack of resources. In this case, tcp stack produced
output that just gone. TSO is there over years and no one even noticed
given TSO/bridge conflict mainly because there is no stats. (IMHO)
Let's blame standards, right? 


Signed-off-by : Vlad Drukker <vlad@storewiz.com>
---
 net/bridge/br_forward.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/net/bridge/br_forward.c b/net/bridge/br_forward.c
--- a/net/bridge/br_forward.c
+++ b/net/bridge/br_forward.c
@@ -31,7 +31,8 @@ static inline int should_deliver(const s

 int br_dev_queue_push_xmit(struct sk_buff *skb)
 {
-       if (skb->len > skb->dev->mtu)
+       /* drop mtu oversized packets except tso */
+       if (skb->len > skb->dev->mtu && !skb_shinfo(skb)->tso_size)
                kfree_skb(skb);
        else {
 #ifdef CONFIG_BRIDGE_NETFILTER


       reply	other threads:[~2005-09-21 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1127239659.12488.26.camel@quant>
     [not found] ` <20050921.001427.27575173.davem@davemloft.net>
2005-09-21 12:53   ` Vlad Drukker [this message]
2005-09-21 16:47     ` [Bridge] Re: [PATCH] TSO fix in br_dev_queue_push_xmit Stephen Hemminger
2005-09-23  6:36     ` David S. Miller

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=1127307186.15678.63.camel@quant \
    --to=vlad@storewiz.com \
    --cc=bridge@osdl.org \
    --cc=davem@davemloft.net \
    --cc=hno@marasystems.com \
    --cc=shemminger@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.