netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Mark Smith <lk-netdev@lk-netdev.nosense.org>
Cc: David Miller <davem@davemloft.net>,
	bcrl@lhnet.ca, opurdila@ixiacom.com, eric.dumazet@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH] net: fast consecutive name allocation
Date: Sat, 14 Nov 2009 17:22:24 -0800	[thread overview]
Message-ID: <20091114172224.5ca4c94e@s6510> (raw)
In-Reply-To: <20091115090604.331d75c2@opy.nosense.org>

On Sun, 15 Nov 2009 09:06:04 +1030
Mark Smith <lk-netdev@lk-netdev.nosense.org> wrote:

> The fundamental purpose of PPPoE is nothing to do with any scaling or
> architecture, it is purely to make a more modern shared networking
> technology like Ethernet look like high speed dial up. This has occurred
> mainly because when broadband came along it allowed ISPs to introduce
> it quickly, without having to also upgrade their dial up oriented
> backend systems i.e. customer authentication/accounting and customer
> support systems. It wasn't ideal then and it isn't ideal now. PPPoE adds
> an overhead of 8 bytes per packet, yet the only thing it is doing is
> changing ethernet from multipoint to point-to-point so PPP can run
> over it and providing ISPs with an ability to identify the subscriber.
> There are other methods to solve customer identity problem without the
> PPPoE overheads. Moving to them however can be a long drawn out process
> because it also means changes to customer's CPE settings, or running
> the old and new methods in parallel for the foreseeable future.

Carriers still haven't figured out that circuit switched networks don't
scale. They just can't learn the lesson of the Internet.

  reply	other threads:[~2009-11-15  1:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  5:01 [net-next-2.6 PATCH] net: fast consecutive name allocation Octavian Purdila
2009-11-13  5:20 ` Octavian Purdila
2009-11-13  6:12   ` Eric Dumazet
2009-11-13  6:26     ` Stephen Hemminger
2009-11-13  7:09       ` Eric Dumazet
2009-11-13  9:51       ` Octavian Purdila
2009-11-13 22:29         ` Stephen Hemminger
2009-11-13 22:40           ` Benjamin LaHaise
2009-11-13 22:49             ` Stephen Hemminger
2009-11-13 23:35               ` Benjamin LaHaise
2009-11-13 23:39                 ` Stephen Hemminger
2009-11-13 23:52                   ` Benjamin LaHaise
2009-11-14  2:59                     ` David Miller
2009-11-14  6:24                       ` Benjamin LaHaise
2009-11-14 22:36                       ` Mark Smith
2009-11-15  1:22                         ` Stephen Hemminger [this message]
2009-11-15  1:49                           ` Mark Smith
2009-11-15  1:55                         ` Denys Fedoryschenko
2009-11-15  7:48                           ` Eric Dumazet
2009-11-15 16:50                           ` Benjamin LaHaise
2009-11-14  7:08               ` Benny Amorsen
2009-11-14  7:21                 ` Eric Dumazet
2009-11-14 16:16                   ` Ben Greear
2009-11-13  9:55     ` Octavian Purdila
2009-11-13 16:40       ` Ben Greear
2009-11-14  0:04   ` Stephen Hemminger
2009-11-14  0:14     ` Octavian Purdila
2009-11-14  0:20       ` Stephen Hemminger

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=20091114172224.5ca4c94e@s6510 \
    --to=shemminger@vyatta.com \
    --cc=bcrl@lhnet.ca \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=lk-netdev@lk-netdev.nosense.org \
    --cc=netdev@vger.kernel.org \
    --cc=opurdila@ixiacom.com \
    /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).