From: Vlad Yasevich <vyasevich@gmail.com>
To: Martin Filip <nexus+kernel@smoula.net>, netdev@vger.kernel.org
Subject: Re: TUN device performance regression
Date: Mon, 14 Apr 2014 09:54:38 -0400 [thread overview]
Message-ID: <534BE89E.70704@gmail.com> (raw)
In-Reply-To: <1397475759.12568.0.camel@interceptor.in.smoula.net>
On 04/14/2014 07:42 AM, Martin Filip wrote:
>> Hello,
>>
>> I've noticed significant TUN device performance drop between 3.13 and
>> 3.14 kernels, problem seems to persist until current git version.
>>
>> With good kernel I can achieve full 100mbps through openvpn without any
>> problem, with problematic kernel TX performance drops down to ~50kbps.
>>
>> According to git bisect it seems that root of all evil is commit
>> 53d6471cef17262d3ad1c7ce8982a234244f68ec.
>>
>> I can confirm that performance is great again with current kernel when I
>> revert this one.
>>
> I've forgot to mention kernel bug:
> https://bugzilla.kernel.org/show_bug.cgi?id=74051
>
Thanks for the report. I am taking a look.
-vlad
next prev parent reply other threads:[~2014-04-14 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 11:31 TUN device performance regression Martin Filip
2014-04-14 11:42 ` Martin Filip
2014-04-14 13:54 ` Vlad Yasevich [this message]
2014-04-14 14:43 ` Vlad Yasevich
2014-04-14 14:51 ` Martin Filip
2014-04-21 14:00 ` Marc Haber
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=534BE89E.70704@gmail.com \
--to=vyasevich@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nexus+kernel@smoula.net \
/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).