Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754225Ab0HBSF0 (ORCPT ); Mon, 2 Aug 2010 14:05:26 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:42580 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753940Ab0HBSFZ convert rfc822-to-8bit (ORCPT ); Mon, 2 Aug 2010 14:05:25 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 2 Aug 2010 19:05:14 +0100 Message-ID: Subject: Re: a Great Idea - include Kademlia networking protocol in kernel From: Valeo de Vries To: hp fk Cc: linux-kernel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1052 Lines: 24 On 2 August 2010 16:33, hp fk wrote: > 2010/8/2 Valeo de Vries : > >> And why exactly can't this be done in userspace? I assume that since >> you mention IP that (perhaps incorrectly) this protocol uses TCP/UDP >> on the lower layers... > > using userspace p2p network service and ?library might be another way > to consolidate the protocol. > in kernel ?or in userspace service/library, each will have its own > advantage and disadvantage. ?like qemu-kvm and qemu userspace. Sorry, but no. You're suggesting adding a protocol to the kernel that fits better in userspace without actually coming up with any reasons why having it in-kernel would be better. Not to mention that adding yet another protocol to the kernel means more vectors for possible exploits. Valeo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/