netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Michal Ostrowski <mostrows@watson.ibm.com>
Cc: rusty@rustcorp.com.au, davem@redhat.com, paulus@samba.org,
	netdev@oss.sgi.com, fcusack@samba.org, dfs@roaringpenguin.com,
	carlson@workingcode.com
Subject: Re: [PATCH, untested] Support for PPPOE on SMP
Date: Wed, 25 Jun 2003 09:15:31 -0700	[thread overview]
Message-ID: <20030625091531.5ebed618.shemminger@osdl.org> (raw)
In-Reply-To: <1056547262.1945.1436.camel@brick.watson.ibm.com>

On 25 Jun 2003 09:21:02 -0400
Michal Ostrowski <mostrows@watson.ibm.com> wrote:

> First some background for those new to this discussion (I was going post
> the original discussion that strted this to this list, but the summary
> here should get everyone up to speed).
> 
> A user has observed a race condition where the last packet of PPPoE
> discovery arrives just before the first payload packet.  The discovery
> packet carries the session id and pppd needs to take this session id and
> create a PPPoE socket which will then pick up all packets matching the
> given session id.  The race is between the arrival of the first payload
> packet and  pppd's creation of the socket that is to receive PPPoE
> payload.  If the packet wins the race, the payload packet is lost.  This
> problem was noticed only because the ISP in this case configured their
> systems to use a longer, non-standard (but legal) retransmit timeout
> thus causing noticeable delays in PPP negotiation.
> 

Also, you only need the ordering dependency till the session is setup, not
after it is established.  Imagine a large ISP with many PPPoE sessions; it
makes no sense to serialize traffic just for this session establishment case.

In the long run, the right answer probably is to push the session management
out of the daemon and into the kernel.  Today the PPPoE code in the kernel
is only half-brained, it needs pppd to survive.

  parent reply	other threads:[~2003-06-25 16:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25  7:24 [PATCH, untested] Support for PPPOE on SMP Rusty Russell
2003-06-25 11:19 ` Jamal Hadi
2003-06-25 13:21 ` Michal Ostrowski
2003-06-25 13:42   ` Michal Ostrowski
2003-06-25 15:45     ` Jamal Hadi
2003-06-25 17:27       ` Michal Ostrowski
2003-06-25 22:17         ` Paul Mackerras
2003-06-25 22:56           ` Michal Ostrowski
2003-06-25 16:15   ` Stephen Hemminger [this message]
2003-06-25 16:22     ` Jamal Hadi
2003-06-25 16:39       ` Stephen Hemminger
2003-06-25 17:07         ` Jamal Hadi
2003-06-25 17:40           ` Stephen Hemminger
2003-06-25 18:00             ` Michal Ostrowski
2003-06-25 22:22           ` Paul Mackerras
2003-06-25 22:53             ` Ben Greear
2003-06-25 21:33   ` David S. Miller
2003-06-25 22:06     ` Michal Ostrowski
2003-06-26  1:04       ` David S. Miller
2003-06-26  3:57     ` Rusty Russell
2003-06-26  3:59       ` David S. Miller
2003-06-26  8:17         ` Rusty Russell
2003-06-26  8:55           ` David S. Miller
2003-06-26 10:47             ` James Carlson
2003-06-26 10:51         ` James Carlson
2003-06-26 23:18           ` Jamal Hadi
2003-06-27 11:39             ` James Carlson
2003-06-27 12:12               ` Paul Mackerras
2003-06-27 13:19                 ` James Carlson
2003-06-27 14:59                 ` Stephen Hemminger
2003-06-27 15:27                   ` James Carlson
2003-06-28  2:21               ` Jamal Hadi
2003-06-28 22:51                 ` Frank Cusack
2003-06-26 11:37       ` Michal Ostrowski
2003-06-25 16:01 ` Jason Lunz

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=20030625091531.5ebed618.shemminger@osdl.org \
    --to=shemminger@osdl.org \
    --cc=carlson@workingcode.com \
    --cc=davem@redhat.com \
    --cc=dfs@roaringpenguin.com \
    --cc=fcusack@samba.org \
    --cc=mostrows@watson.ibm.com \
    --cc=netdev@oss.sgi.com \
    --cc=paulus@samba.org \
    --cc=rusty@rustcorp.com.au \
    /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).