netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J Chapman" <jchapman@katalix.com>
To: "'Herbert Xu'" <herbert@gondor.apana.org.au>,
	"'David S. Miller'" <davem@davemloft.net>
Cc: <kuznet@ms2.inr.ac.ru>, <jmorris@redhat.com>,
	<netdev@oss.sgi.com>, <linux-ppp@vger.kernel.org>,
	<paulus@samba.org>
Subject: RE: single process pppd for all PPP sessions? [Was [IPCOMP] Use per-cpu buffers]
Date: Mon, 13 Sep 2004 12:18:39 +0100	[thread overview]
Message-ID: <200409131119.i8DBJSgn007059@oss.sgi.com> (raw)
In-Reply-To: <20040910111047.GA29330@gondor.apana.org.au>

Re: anyone think of doing a single process PPP daemon managing all 
PPP sessions?

Yes, although nothing started yet. Still working on OpenL2TP...
http://openl2tp.sf.net/

-James

> -----Original Message-----
> From: Herbert Xu [mailto:herbert@gondor.apana.org.au] 
> Sent: 10 September 2004 12:11
> To: David S. Miller
> Cc: kuznet@ms2.inr.ac.ru; jmorris@redhat.com; netdev@oss.sgi.com;
linux-ppp@vger.kernel.org; paulus@samba.org
> Subject: Re: [IPCOMP] Use per-cpu buffers
> 
[snip]

> On a totally orthogonal topic, has any body thought of doing a PPP
> daemon like the IPsec daemons? That is, have one process that manages
> all PPP sessions.  This could be useful for large L2TP servers and
> alike.
>

      parent reply	other threads:[~2004-09-13 11:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 12:22 [IPCOMP] Use per-cpu buffers Herbert Xu
2004-09-09 16:16 ` David S. Miller
2004-09-10 11:10   ` Herbert Xu
2004-09-10 15:42     ` James Morris
2004-09-10 21:55       ` David S. Miller
2004-09-10 22:33       ` Herbert Xu
2004-09-13 11:18     ` J Chapman [this message]

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=200409131119.i8DBJSgn007059@oss.sgi.com \
    --to=jchapman@katalix.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jmorris@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-ppp@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=paulus@samba.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).