All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: netdev@vger.kernel.org
Cc: Vlad Yasevich <vyasevic@redhat.com>, wshuman3@gmail.com
Subject: Fwd: [Bug 73891] New: Slow Transfer Speeds though openconnect, Juniper SSL vpns
Date: Sat, 12 Apr 2014 20:18:01 +0200	[thread overview]
Message-ID: <53498359.8000302@redhat.com> (raw)
In-Reply-To: <bug-73891-65011@https.bugzilla.kernel.org/>

-------- Original Message --------
Subject: [Bug 73891] New: Slow Transfer Speeds though openconnect, Juniper SSL vpns
Date: Sat, 12 Apr 2014 15:35:52 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: dborkman@redhat.com

https://bugzilla.kernel.org/show_bug.cgi?id=73891

             Bug ID: 73891
            Summary: Slow Transfer Speeds though openconnect, Juniper SSL
                     vpns
            Product: Networking
            Version: 2.5
     Kernel Version: 3.14
           Hardware: All
                 OS: Linux
               Tree: Mainline
             Status: NEW
           Severity: normal
           Priority: P1
          Component: Other
           Assignee: shemminger@linux-foundation.org
           Reporter: wshuman3@gmail.com
         Regression: No

There was a regression in 3.14 which caused slow transfer speeds noticed when
connected to openconnect and juniper ssl vpns.

There was also a discussion about this on the mailing list
https://lkml.org/lkml/2014/4/2/317

I had time to bisect.
# first bad commit: [53d6471cef17262d3ad1c7ce8982a234244f68ec] net: Account for
all vlan headers in skb_mac_gso_segment

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

           reply	other threads:[~2014-04-12 18:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-73891-65011@https.bugzilla.kernel.org/>]

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=53498359.8000302@redhat.com \
    --to=dborkman@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevic@redhat.com \
    --cc=wshuman3@gmail.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 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.