Re: [Xen-devel] n/w performance degradation

[Diwaker Gupta <diwaker.lists@xxxxxxxxx>]

> We used to be able to saturate GigE with a single CPU, although

Same here.

> admittedly burning quite a bit more CPU than using dom0 as the
> endpoint. I guess things have got out of tune, but there are a bunch of
> things we could do to encourage I/O batching ('x packets or y
> milliseconds' style receive batching, and transmitting batches of
> packets every x milliseconds or when the domU goes idle). This,
> together with scheduler tuning, should definitely get the performance
> back, although its a balancing act with one CPU to ensure no stage of
> the I/O processing pipeline gets starved.

Look forward to it. Whats the deal with the pipelined backend? Whats
the target scenario there?

Meanwhile, though I agree that SMPs and hyperthreaded processors are
becoming the norm, it still doesn't solve this problem. Even on an SMP
machine, I can have dom0 co-located with a VM on the same CPU, and I'm
not sure how different that would be from the current situation.

On a related note, has anyone been working on the IDD stuff? Is it
possible to wrap up a device driver in its own domain? The last time 
I tried, it basically wasn't possible, but I'd really be interested in
helping out any which way to get it working.

Diwaker
--
Web/Blog/Gallery: http://floatingsun.net

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel