Fernando Luis Vázquez Cao wrote:
>
> *** Goals
> 1. Cgroups-aware I/O scheduling (being able to define arbitrary
> groupings of processes and treat each group as a single scheduling
> entity).
> 2. Being able to perform I/O bandwidth control independently on each
> device.
> 3. I/O bandwidt
[EMAIL PROTECTED] wrote:
> On Sunday 10 June 2007, Avi Kivity wrote:
>>> - PCI (or your favorite HW bus) passthrough, for your favorite
>>> oddball device (e.g., crypto-accelerators).
>>>
>> Won't all high-bandwidth traffic be through dma, bypassing virtio?
>
> It can be done, but you'd also ne
[EMAIL PROTECTED] wrote:
> On Wednesday 13 June 2007, Caitlin Bestler wrote:
>>
>>> It can be done, but you'd also need a passthrough for the IOMMU in
>>> that case, and you get a potential security hole: if a malicious
>>> guest is smart enough to figure
Arnd Bergmann wrote:
> On Thursday 14 June 2007, Caitlin Bestler wrote:
>>
>> Why not simply adopt the policy that if the IOMMU does not meet the
>> security requirements of the Hypervisor then it is not an IOMMU as
>> far as the Hypervisor is concerned?
>>
>
[EMAIL PROTECTED] wrote:
> On Wed, 2007-07-11 at 12:28 +0200, Christian Borntraeger wrote:
>> Am Mittwoch, 4. Juli 2007 schrieb Rusty Russell:
>>> +static void try_fill_recv(struct virtnet_info *vi)
>
>> Hmm, so it allocates skbs until oom or until add_buf fails, right?
>
> Yep.
>
>> Do you expe
