All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Valdis.Kletnieks@vt.edu
Cc: hp fk <fkhp101@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: a Great Idea - include Kademlia networking protocol in kernel
Date: Mon, 02 Aug 2010 11:16:12 -0700	[thread overview]
Message-ID: <4C570B6C.201@zytor.com> (raw)
In-Reply-To: <8023.1280761746@localhost>

On 08/02/2010 08:09 AM, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 02 Aug 2010 23:02:01 +0800, you said:
> 
>>  HTTP if more of an access protocol,the logical network is woven in
>> the web page controled by html, the network needed is formed and take
>> part in by tcp/ip protocol which usually lies in kernel.
>>
>> Kademlia itself has the responsibility to weave the p2p network and
>> bring a node into the p2p network before access can be done.
> 
> You're still failing to explain why the kernel needs to do this
> rather than some -lkademlia in userspace.
> 

Specifically, the reasons a network protocol goes in the kernel is
either because it needs a multiplex that isn't possible in userspace
(UDP, for example, needs a port number multiplex), or because acceptable
performance isn't possible in userspace (this mostly applies to NFS.)

	-hpa


  reply	other threads:[~2010-08-02 18:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 12:24 a Great Idea - include Kademlia networking protocol in kernel hp fk
2010-08-02 12:46 ` Valeo de Vries
     [not found]   ` <AANLkTimFhNG0WVXURsjhHAisbrAK20zFgReydJ6AG1WJ@mail.gmail.com>
2010-08-02 18:05     ` Valeo de Vries
2010-08-02 12:56 ` Valdis.Kletnieks
     [not found]   ` <AANLkTi=keL2rUzxdxgscTU9cQSNxOnAtGVuAwTq9Wfuq@mail.gmail.com>
2010-08-02 14:29     ` hp fk
2010-08-02 14:42       ` Damjan Jovanovic
     [not found]     ` <6501.1280759131@localhost>
2010-08-02 15:02       ` hp fk
2010-08-02 15:09         ` Valdis.Kletnieks
2010-08-02 18:16           ` H. Peter Anvin [this message]
2010-08-02 13:16 ` Fwd: " hp fk
2010-08-02 13:51   ` Paulius Zaleckas
2010-08-03 10:44 ` Bernd Petrovitsch
2010-08-03 11:15   ` Valeo de Vries

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=4C570B6C.201@zytor.com \
    --to=hpa@zytor.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=fkhp101@gmail.com \
    --cc=linux-kernel@vger.kernel.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.