All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Marcos <stalkingtime@gmail.com>
Cc: netdev@vger.kernel.org, Stephen Guerin <stephen@sfcomplex.org>
Subject: Re: Fwd: a Great Idea - include Kademlia networking protocol in kernel -- REVISITED
Date: Sun, 14 Nov 2010 10:39:04 +0100	[thread overview]
Message-ID: <1289727544.2743.72.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTimkPpWob8ANySeWBvDE+Pq2wy4SQWJOSYzbS7QG@mail.gmail.com>

Le dimanche 14 novembre 2010 à 02:14 -0700, Marcos a écrit :
> > I have no idea why and how kademlia would be added to "linux kernel"
> >
> > Its a protocol based on UDP, and probably already done on userland.
> >
> > What am I missing ?
> 
> The idea is to tightly couple it to the operating system to create a
> sort of "super operating system" that is seamless to the application
> layers above.  Just like memory stores are tightly integrated as to be
> unnoticeable....
> 

But we dont want a "super operating system". We want a good one.

Memory stores done in userland are as fast as memory stores done in
kernel.

Once you need to access files, perform complex searches, timers,
logging, and all the stuff, you really want to do it from userland, in
high level language that many programmers master, or get something that
is too complex/buggy.




  reply	other threads:[~2010-11-14  9:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14  6:31 a Great Idea - include Kademlia networking protocol in kernel -- REVISITED Marcos
2010-11-14  7:21 ` Fwd: " Marcos
2010-11-14  8:50   ` Eric Dumazet
2010-11-14  9:14     ` Marcos
2010-11-14  9:39       ` Eric Dumazet [this message]
2010-11-16  6:21         ` Marcos
2010-11-16 16:11           ` Honglei Cong
2010-11-18 22:21             ` Marcos
2010-11-15 10:55       ` Chris Snook

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=1289727544.2743.72.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stalkingtime@gmail.com \
    --cc=stephen@sfcomplex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.