linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristian Evensen <kristian.evensen@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: PPP and buffer sizes
Date: Thu, 14 Jan 2010 22:19:05 +0000	[thread overview]
Message-ID: <4B4F9859.1050909@gmail.com> (raw)

Hello,

I am trying to debug a performance issue I am experiencing with 
L2TP-tunnels (created using xl2tpd). When I measure the UDP-performance 
of different desired throughputs using iperf together with the tunnel, I 
see that the throughput stabilizes at a certain speed while the packet 
loss increases. When I measure the performance using TCP together with 
the tunnel, I see a very high number of packet losses, forcing 
congestion control and resulting in a significantly lower throughput 
than without tunneling.

I guess this is caused by buffers being filled up and packets are 
dropped, however, I have not been able to figure out which buffer or 
exactly why this happens. If I remove the tunnels and measure the 
performance, the maximum supported throughput by the network is reached, 
so both the UDP and TCP send and receive buffers are big enough. I have 
also measured the processing delay caused by the L2TP-software and that 
is at most 50 microseconds, which should not affect the results.

L2TP passes packets to PPP after they have been decapsulated and, as far 
as I have understood, PPP + IP layer processing (which is on microsecond 
scale) is the last step before the packet is sent to the application 
layer. My question is therefore, is there anything in PPP that can 
explain what I am experiencing?

Thanks in advance for any help,
Kristian

                 reply	other threads:[~2010-01-14 22:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B4F9859.1050909@gmail.com \
    --to=kristian.evensen@gmail.com \
    --cc=linux-ppp@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).