netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ortwin Glück" <odi@odi.ch>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: 3.14 regression: huge latency in read/select on tun
Date: Wed, 02 Apr 2014 18:17:34 +0200	[thread overview]
Message-ID: <533C381E.9090103@odi.ch> (raw)

Hi,

Since 3.14 the openconnect VPN tunnel becomes unusable for me because
packets appear on the tun device at a horribly low rate. 3.12 and 3.13
do not exhibt the problem.

Here is an strace of openconnect trying to read from its fd
  7 -> /dev/net/tun

15:07:33.130640 read(7, 0x1e05e58, 1280) = -1 EAGAIN (Resource
temporarily unavailable)
===> should return available data already
15:07:33.130745 select(8, [3 6 7], [], [6], {30, 0}) = 1 (in [7], left
{29, 783272})
===> HUGE 217ms delay here
15:07:33.347681 read(6, 0x1dfc973, 5)   = -1 EAGAIN (Resource
temporarily unavailable)
15:07:33.347806 read(7,
"E\10\5\0b\343@\0@\6\17~\n\363X\236\n\271UE\222:\0\26\37O\7\342\315\21q\33"...,
1280) = 1280


The send queue of the socket being routed via the tun device has a lot
of outstanding data (here an scp/ssh upload):
tcp        0  29788 local:46577  remote:22   ESTABLISHED

(IPs replaced for privacy)

toggling TCP autocorking has no influence.

Any ideas what could be the culprit?

Ortwin

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 16:17 Ortwin Glück [this message]
2014-04-02 16:42 ` 3.14 regression: huge latency in read/select on tun Eric Dumazet
2014-04-03  7:52   ` Ortwin Glück
2014-04-03 13:19     ` Eric Dumazet
2014-04-03 13:50       ` Eric Dumazet
2014-04-04  8:34         ` Ortwin Glück
2014-04-19 20:13         ` Ortwin Glück
2014-04-20 16:31           ` Eric Dumazet
2014-04-21  8:40             ` Ortwin Glück
2014-04-21 11:13               ` Lukas Tribus

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=533C381E.9090103@odi.ch \
    --to=odi@odi.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).