lkml.org 
[lkml]   [2004]   [Apr]   [7]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
    /
    DateWed, 7 Apr 2004 17:05:16 +0200
    FromLars Marowsky-Bree <>
    SubjectRe: Rewrite Kernel
    Guys, gals,
    
    you are all missing the point.
    
    It is obvious that what we really need is a hand-optimized in-kernel
    core LISP machine written in >i386 assembly, then we need to port the
    rest of the kernel to run as LISP bytecode on top of that in ring1 (in
    particular the security policies).
    
    Of course, important privileged user-space such as glibc should be
    ported to this highly efficient non-recursive LISP machine too for
    efficiency and run on ring 2 for speed and security.
    
    As a further benefit, this could provide us with a stable kernel binary
    ABI via the LISP interfaces to which we could dynamically translate the
    existing kernel modules on load, for which nvidia and the binary-only
    Inifiband stack seem perfect candidates to secure industry buyin.
    
    Oh, and of course this project needs to be managed via BitKeeper.
    
    
    Sincerely,
        Lars Marowsky-Brée <lmb@suse.de>
    
    -- 
    High Availability & Clustering	      \ ever tried. ever failed. no matter.
    SUSE Labs			      | try again. fail again. fail better.
    Research & Development, SUSE LINUX AG \ 	-- Samuel Beckett
    -
    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/
    
    
    \
     
     \ /
      Last update: 2005-03-22 14:02    [from the cache]
    ©2003-2008