Hey.
Im having problems understanding relation between classic
(ip_input.c) and fast (ip_flow.c) forwarding. Could
anyone please explain what exactly is the difference, which mechanism
is used when, and what is corelation
between those two ? I'll be grateful for any response. If it's not the
On Fri, Jul 09, 2010 at 01:15:58PM +0200, Putrycy wrote:
Im having problems understanding relation between classic
(ip_input.c) and fast (ip_flow.c) forwarding. Could
anyone please explain what exactly is the difference, which mechanism
is used when, and what is corelation between those two ?
On Mon Jul 12 2010 at 01:51:54 +0200, Jean-Yves Migeon wrote:
Anyway, the solution as usual is to work the problem from both ends
(improve the server methods and the kernel drivers) and perform a
meet-in-the-middle attack at the sweet spot where nothing is lost and
everything is gained.
On 12.07.2010 16:41, Antti Kantee wrote:
It's not the same thing. Correct me if I misunderstood, but I thought
you want to port/adjust/whatever rumpuser to the xen hypercall interace.
Since the xen hypervisor interface, as opposed to a posix process
environment, is designed for hosting an OS,
On 12.07.2010 18:41, Antti Kantee wrote:
On Mon Jul 12 2010 at 18:32:01 +0200, Jean-Yves Migeon wrote:
On 12.07.2010 18:03, Antti Kantee wrote:
Now, why do you expect this to not work like it does with the current
style of dom0? ... aah, currently everything just goes to dom0, and
now you'd