LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michel Machado <michel@digirati.com.br>
To: Alex Elsayed <eternaleye@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux XIA - merge proposal
Date: Thu, 05 Mar 2015 13:34:56 -0500	[thread overview]
Message-ID: <54F8A1D0.308@digirati.com.br> (raw)
In-Reply-To: <54F5EF6E.9090303@digirati.com.br>

 >>    We have been developing Linux XIA, a new network stack that
 >> emphasizes evolvability and interoperability, for a couple of years,
 >> and it has now reached a degree of maturity that allows others to
 >> experiment with it.
 >
 > From looking at your wiki, "network stack" may have been a poor
 > choice of term - it looks like rather than being a new network
 > stack (which in Linux, is commonly used to refer to the software
 > stack that lives between the APIs and the hardware), this is a
 > new protocol (and framework _for_ protocols) operating at
 > the same level of the network as IP, with ideas extending
 > upwards through TCP.
 >
 > Now, that's a rather different proposal - witness that RDS, TIPC,
 > etc all made it into the kernel relatively easily, especially when
 > compared to netmap, or any other system that tried to replace
 > the Linux networking infrastructure.

Hi Alex,

    Thank you very much for having caught this definition mismatch! I 
personally see TCP/IP as a network stack on its own right. From this 
perspective, XIA, TCP/IP, RDS, and TIPC are all at the same level as you 
concluded. I don't mind adopting the definitions that are more common 
among kernel developers.

    Linux XIA is not replacing the other protocols (using your 
definition). Linux XIA is another protocol, and, as you correctly 
pointed out: a framework for other protocols.

[ ]'s
Michel Machado

  parent reply	other threads:[~2015-03-05 18:35 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
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 [this message]
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=54F8A1D0.308@digirati.com.br \
    --to=michel@digirati.com.br \
    --cc=eternaleye@gmail.com \
    --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).