From: David Miller <davem@davemloft.net>
To: tom@herbertland.com
Cc: chris@logicalelegance.com, netdev@vger.kernel.org
Subject: Re: Time to revisit LISP?
Date: Thu, 03 Nov 2016 17:00:18 -0400 (EDT) [thread overview]
Message-ID: <20161103.170018.314857405677363551.davem@davemloft.net> (raw)
In-Reply-To: <CALx6S34-b0dDL0xOvjU+uDzwsZHAt4QPfpHrpeauMmMh4MTKXA@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 3 Nov 2016 13:57:59 -0700
> On Thu, Nov 3, 2016 at 1:37 PM, David Miller <davem@davemloft.net> wrote:
>> Userspace resolution of paths in response to data path signalling
>> simply does not scale and is fundamentally an extremely poor design
>> choice. We're trying to move away from, rather than towards, these
>> kinds of architectures.
>
> OVS is quite different I think. LISP is a specific resolution protocol
> of identifier to locator as opposed to be some open ended mechanism to
> resolve some arbitrary definition of flows like OVS. Also, I don't
> think there's any specific requirement in LISP that prevents on from
> implementing the mapping protocol in the kernel, it should just be a
> simple UDP communication.
>
> Do you see anything in the protocol itself that would be a showstopper?
I'd have to see the code and how it works. I can't review hypothetical
implementations.
prev parent reply other threads:[~2016-11-03 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 19:22 Time to revisit LISP? Tom Herbert
2016-11-03 20:37 ` David Miller
2016-11-03 20:57 ` Tom Herbert
2016-11-03 21:00 ` David Miller [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=20161103.170018.314857405677363551.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chris@logicalelegance.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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).