Fwd: request for stand (Toro Project)

[Matias Vara larsen]

Dears,

I am Matias Vara and Tias Guns has just suggested me that my proposal for a stand fits better as lightningtalk at the microkernel devroom. 
However, the deadline for such talks already past. There is any possibility to consider my proposal for stand as a proposal for a lighningtalk ? 

Thanks in advance, Matias.


----- Mensaje reenviado -----
> De: "Tias Guns" <tias at fosdem.org>
> Para: "Matias Vara larsen" <matias.vara_larsen at inria.fr>, stands at fosdem.org
> Enviados: Martes, 2 de Diciembre 2014 22:09:04
> Asunto: Re: request for stand (Toro Project)
> 
> Hi Matias,
> 
> Thank you for your stand proposal. It has been added to the list of
> candidates.
> 
> I must add that a topic like the one you propose makes much more chance
> as a lightningtalk (see website), then as a stand.
> 
> Actually, perhaps the best place would be the devroom about microkernels:
> https://lists.fosdem.org/pipermail/fosdem/2014-November/002061.html
> 
> Please contact them ASAP as the deadline may be near or have already
> past. Feel free to include this communication in it.
> 
> 
> Kind regards,
> Tias
> 
> On 11/19/2014 03:25 PM, Matias Vara larsen wrote:
> > Dears,
> >
> > I am Matias Vara (http://www-sop.inria.fr/members/Matias.Vara_Larsen/),
> > founder and main developer of TORO since 2006. Currently, I am doing a
> > PhD in Computer Science at INRIA, Nice, France. In this email, I am
> > proposing a stand about Toro Kernel project
> > (http://sourceforge.net/projects/toro/,
> > http://torokerneleng.blogspot.com/).
> > In systems with high-grade multiprocessing, we have identified two
> > bottlenecks: in the accessing of the memory bus and in the shared
> > resources. To deal with these issues, we propose a dedicated kernel
> > named TORO that is optimized to run a single multi-threading
> > application. TORO is demonstrating an innovative operating system by
> > integrating at the same ring level both kernel and the user application
> > server. In addition, the accessing to resources (e.g., Filesystem,
> > Networking, Memory) is dedicated to specific processor. Then, only the
> > CPU where is dedicated the resource is allowed to access to the instance
> > of the resource. As a result of this design, the kernel provides direct
> > access to all resources without any overhead, and therefore maximizes
> > performance for the overall system.
> > To sum-up the approach, in TORO, the threads of the user application
> > server are distributed evenly on all CPUs and running independently in
> > parallel. The memory model chosen is NUMA without pagination. During the
> > initialization, the memory is divided proportionally for each processor
> > installed on the system. When a thread needs memory, the memory
> > allocator returns a free block of memory depending on which CPU the
> > thread is running. In the same way, TORO can dedicate resources to
> > specific processor, i.e., a FileSystem. This only CPU then can access to
> > this instance of FileSystem. The scheduler is based on the cooperative
> > threading model, therefore due to this design, TORO can migrate threads
> > between CPUs and send messages between threads without using any lock
> > instruction.
> > FOSDEM is a very good place to discuss general purpose operating systems
> > vs. dedicated operative systems. This discussion can be motivated by
> > showing the characteristics of TORO. To do so, I am proposing a stand
> > with a poster and examples of applications ported to TORO. The aim of
> > the poster is to show the goals of the kernel, thus highlighting the
> > main differences with a general purpose OS. The examples aim to show how
> > the main goals of the kernel have been implemented. These examples are
> > currently in the git repository of TORO, and can be easily tested in a
> > virtual machine like QEMU or Bochs.
> >
> > Kinds Regards, Matias.
> >
> >
> > _______________________________________________
> > stands mailing list
> > stands at lists.fosdem.org
> > https://lists.fosdem.org/listinfo/stands
> >
> 
>