netdev - Re: Fwd: a Great Idea - include Kademlia networking protocol in kernel -- REVISITED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTik-oLx5B2t0E3XKsseHi7tJF2hDMkOw21Mt=i0F@mail.gmail.com>
Date:	Thu, 18 Nov 2010 15:21:25 -0700
From:	Marcos <stalkingtime@...il.com>
To:	Honglei Cong <conghonglei@...il.com>, netdev@...r.kernel.org
Subject: Re: Fwd: a Great Idea - include Kademlia networking protocol in
 kernel -- REVISITED

>> Yes, of course, all that will have to be considered.   But I'm
>> suggesting that such a move is an investment in the future, that the
>> the number of machines that will want or request peer-2-peer
>> connectivity will (or should) only increase.  Done right, such a move
>> should *simplify* things.  We're biased to think in centralized ways
>> because of the centuries-old history of *who* has the resources.  But
>> as networking, computation, and storage become commodified further,
>> whole new topologies for the *right* architecture become available.
>> The idea of "the OS" itself morphs.   And the *only* way maximize the
> Agree with u.  But 'kernel' is not.

...Consider a unified model of two orthogonal resources: processor --
memory.  In theory such a unified model should be realizable.  For
example, if we fix the processor side (say the user's machine), then
you can move around the memory side, unify different memory stores:
cache, RAM, local HD, Networked file storage (naturally logarithmic
scaling).  There's no more need to "install applications":  it's all
installed out there somewhere (probably from the same place where it
was created), you just need to "page it in".  Create an abstract,
user-controlled, peer grouping model that allows arbitrary "trust (or
privacy) groups" where "node discovery" (say new annoucements) and
"shared memory" is allowed and watch the Social Linux Network Brain
evolve.  (I better not even mention an integrated voting model
yet....)

Too idealistic?

marcos
pangaia.sourceforge.net
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html