From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752575AbbCZQbM (ORCPT ); Thu, 26 Mar 2015 12:31:12 -0400 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]:39241 "EHLO mail.sfc.wide.ad.jp" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751227AbbCZQbD (ORCPT ); Thu, 26 Mar 2015 12:31:03 -0400 X-Greylist: delayed 386 seconds by postgrey-1.27 at vger.kernel.org; Thu, 26 Mar 2015 12:31:02 EDT Date: Fri, 27 Mar 2015 01:24:34 +0900 Message-ID: From: Hajime Tazaki To: richard@nod.at Cc: linux-arch@vger.kernel.org, arnd@arndb.de, corbet@lwn.net, cl@linux.com, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, netdev@vger.kernel.org, linux-mm@kvack.org, jdike@addtoit.com, rusty@rustcorp.com.au, mathieu.lacage@gmail.com Subject: Re: [RFC PATCH 00/11] an introduction of library operating system for Linux (LibOS) In-Reply-To: <55133BAF.30301@nod.at> References: <1427202642-1716-1-git-send-email-tazaki@sfc.wide.ad.jp> <551164ED.5000907@nod.at> <55117565.6080002@nod.at> <55118277.5070909@nod.at> <55133BAF.30301@nod.at> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) X-Face: "+?b:_s\r$dbBx'Ur*k#`5|~\>v~i`PzaxANTx_S?J>:mTQrtm:c7'f5b~W2eX~Fl[0Pw,0bow)8r8Z5,D&>]C/'ujqr:fbY>]/52T^Q~cX*y5\?!"i<^Vp=zCNguAeyPH$`ZTv{di25X8,%@! MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Richard, At Wed, 25 Mar 2015 23:50:23 +0100, Richard Weinberger wrote: > > Hi! > > Am 25.03.2015 um 15:48 schrieb Hajime Tazaki: > > > > At Tue, 24 Mar 2015 16:27:51 +0100, > > Richard Weinberger wrote: > >> > >> I'd say you should try hard to re-use/integrate your work in arch/um. > >> With um we already have an architecture which targets userspace, > >> having two needs a very good justification. > > > > in addition to the case of my previous email, libos is not > > limited to run on user-mode: it is just a library which can > > be used with various programs. thus it has a potential (not > > implemented yet) to run on a hypervisor like OSv or MirageOS > > does for application containment, or run on a bare-metal > > machine as rumpkernel does. We already have a clear > > interface for the underlying layer to be able to add such > > backend. > > > > again, it's not only for user-mode. > > > > mixing all the stuff in a single architecture may not only > > mislead to users, but also introduce conceptual-disagreements > > during code sharing of essential parts. > > > > I don't see any benefits to have a name 'um' with this idea. > > > > # I'm not saying sharing a part of code is bad idea at all, btw. > > After digging into the source I know what you mean and I have the thank you for your deep review on the source code ! > feeling that "lib" is the wrong name. > It has not much do to with an architecture. could you care to elaborate your feeling more explicitly ? what is an architecture here and what is _not_ an architecture ? is UML an architecture in your sense (probably yes, but why)? and what is arch/lib missing for an architecture ? > Apart from that, I really like your idea! great to hear that ;) > You don't implement an architecture, you take some part of Linux > (the networking stack) and create stubs around it to make it work. > That means that we'd also have to duplicate kernel functions into > arch/lib to keep it running. again, the above same questions. it (arch/lib) is a hardware-independent architecture which provides necessary features to the remainder of kernel code, isn't it ? answers to those questions are really helpful for a feedback on this RFC patches. > BTW: It does not build here: > ---cut--- > LIB liblinux-4.0.0-rc5.so fixed, thanks: though the issue was in the external code base (i.e., linux-libos-tools). there was a parallel build (make -jX) problem. # you may need to git pull at arch/lib/tools to reflect the updates. thanks. -- Hajime