LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michel Machado <michel@digirati.com.br>
To: Daniel Borkmann <daniel@iogearbox.net>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux XIA - merge proposal
Date: Tue, 03 Mar 2015 19:31:58 -0500	[thread overview]
Message-ID: <54F6527E.6080406@digirati.com.br> (raw)
In-Reply-To: <54F64B75.3010109@iogearbox.net>

Hi Daniel,

>> We're fine with clearly marking Linux XIA as being under staging
>> as well as helping to define this review process for network stacks.
>
> With regard to staging, the code there is usually horrible and I'm
> not sure anyone really looks there, that would mitigate the review
> problem to the time when you try to get it out from there, so I'm
> not sure it brings anything. ;)

    I suggested staging as a way to incrementally review the code. XIA 
is very modular, each component is a kernel module. So one can review a 
kernel module at a time. My intention is to lower the review burden as 
much as I can. I'm open to suggestions to work this out.

> +1 on what Eric said, would have also been nice if you had clearly
> described in your mail (w/o buzz words) what it is and what it does.

    XIA is not an incremental design over IP, and a reasonable 
explanation would've made my e-mail exceeding large. Our wiki has a lot 
content explaining the design as well as demoing it, and I can answer 
questions here, or through another communication medium that you guys 
feel comfortable.

> Are you trying to introduce a new network stack as an alternative
> to the current one, e.g. something like FreeBSD's netgraph?

    I'm trying to introduce a new network stack that enables one to 
implement network designs that are incompatible with IP for a reason or 
another. On top of that, these designs, once ported to Linux XIA, could 
be combined to work together as we tried to highlight in the following demo:

https://github.com/AltraMayor/XIA-for-Linux/wiki/An-exemplifying-demo

    There're a good number of designs in the literature that hasn't seen 
the sun light because they are hard to experiment with since they are 
not compatible with IP. Our hope is to bring these designs to life and 
have a true evaluation of them. That is, we hope that Linux XIA will 
enable the community at large to crowdsource the future Internet. We 
work this vision out in this technical report:

http://www.cs.bu.edu/techreports/pdf/2015-001-linux-xia.pdf

[ ]'s
Michel Machado

  reply	other threads:[~2015-03-04  0:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 17:29 Michel Machado
2015-03-03 23:33 ` Eric W. Biederman
2015-03-04  0:14   ` Michel Machado
2015-03-04  0:01 ` Daniel Borkmann
2015-03-04  0:31   ` Michel Machado [this message]
2015-03-04  5:49     ` Greg KH
2015-03-04 13:01       ` Michel Machado
2015-03-05 16:31 ` Alex Elsayed
2015-03-05 18:34 ` Michel Machado
2015-03-10 17:01 ` Bjorn Helgaas
2015-03-10 17:19   ` Eric Dumazet
2015-03-10 22:01     ` Bjorn Helgaas
2015-03-13 15:26   ` Michel Machado
2015-03-15  9:37     ` Greg KH
2015-03-15 10:03       ` Oded Gabbay
2015-03-17 12:37         ` Michel Machado
2015-03-17 12:25       ` Michel Machado
2015-03-18 10:27         ` Oded Gabbay
2015-03-20 18:46           ` Michel Machado
2015-03-20 19:41             ` Bjorn Helgaas

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=54F6527E.6080406@digirati.com.br \
    --to=michel@digirati.com.br \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --subject='Re: Linux XIA - merge proposal' \
    /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

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).