public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Nuri Jawad <lkml@jawad.org>
To: netdev@vger.kernel.org
Cc: akpm@osdl.org
Subject: Re: Fw: Bug: PPP dropouts in >=2.6.16
Date: Tue, 2 May 2006 22:55:17 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605022233180.21275@pc> (raw)
In-Reply-To: <Pine.LNX.4.64.0604301520030.5512@pc>

Good evening,

Bugzilla entry on this is now here:
http://bugzilla.kernel.org/show_bug.cgi?id=6484

Note the interesting fact that kernel mode PPPoE is not affected. Thus it 
could also be a bug in Roaring Penguin's PPPoE program. The problem is 
that all other user space implementations seem to be quite outdated
(made for 2.2 kernels).

I still did observe around 500 packets being lost after a night of pinging 
this machine, compared to around 30 with 2.6.15.7 user mode pppoe and 
700-1100 with >=2.6.16 user mode. I made a little perl script that 
generates a histogram from ping's output and there were only single 
packets lost.
However, just when I was about to test kernel mode with 2.6.15.7 tonight, 
this effect disappeared. Might have been my ISP after all.

Thus, for the time being, kernel mode PPPoE seems to be a viable 
workaround.
The whole matter is a bit strange to me. I would have expected that the 
kernel only communicates with pppd which then utilizes a process 
encapsulating the packts in ethernet frames. That's why I didn't
think this bug was a pure pppoe issue, which it seems to be.

Regards, Nuri

  reply	other threads:[~2006-05-02 20:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0604202217450.4014@pc>
2006-04-30 11:43 ` Fw: Bug: PPP dropouts in >=2.6.16 theosch
2006-04-30 12:05   ` theosch
2006-04-30 14:10   ` Nuri Jawad
2006-05-02 20:55     ` Nuri Jawad [this message]
2006-04-21  8:08 Andrew Morton
2006-04-21 17:15 ` Jesse Brandeburg
2006-04-21 18:56   ` Andrew Morton
2006-04-22  0:02   ` Andi Kleen
2006-04-24  7:41     ` Sven Schuster
2006-04-26  0:36       ` Nuri Jawad
2006-04-26  6:04         ` Sven Schuster
2006-04-29  0:05           ` Nuri Jawad
2006-04-26 21:25         ` Sven Schuster
2006-04-26 22:07           ` Andrew Morton
2006-04-27  5:48             ` Sven Schuster

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=Pine.LNX.4.64.0605022233180.21275@pc \
    --to=lkml@jawad.org \
    --cc=akpm@osdl.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