Hi Antti, On 06/03/2016 11:36 AM, Antti Kantee wrote:
On 03/06/16 09:30, Pravin wrote:
Rump kernels do not provide a libc, Rumprun does. I didn't design Rumprun to be used for portable drivers, I did (partially) design rump kernels for that purpose. Is there some reason why you are not integrating just rump kernels instead of the Rumprun stack?
The motivation to go for rumprun was lack of clear understanding of the rumpkernel, and it seemed easy (and cleaner) to add Barrelfish as an additional platform to rumprun due to the Non-POSIX'y nature of Barrelfish. My guess was that keeping the changes limited to the 'rumprun/platform/' would be self-contained, and would simplify the maintenance of the code. I am open for suggestions if my initial approach seems ill-suited. My goal is to be able to use NetBSD TCP/IP stack from Barrelfish applications as a library, and if possible, ability to easily track the updates to rump kernel. Currently I am looking into using '-k' flag of rumprun to avoid linking with libc, and I will be happy to hear about alternate approaches or any suggestions. Regards, Pravin
