Re: [PATCH 5/5] ioeventfd: Introduce KVM_IOEVENTFD_FLAG_SOCKET

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 14, 2011 at 11:09 AM, Avi Kivity <avi@xxxxxxxxxx> wrote:
> On 07/14/2011 10:26 AM, Pekka Enberg wrote:
>>
>> On 7/13/11 4:32 PM, Avi Kivity wrote:
>>>
>>> Just how fast do you type?
>>>
>>> It's not enough to make something faster, it has to be slow to being
>>> with.  The interface is good, but use it where it helps.
>>
>> I don't know why you bring up serial console input here. Sasha's
>> original KVM_IOEVENTFD_FLAG_PIPE patch clearly stated:
>>
>>  A simple example for practical use is the serial port. we are not
>>  interested in an exit every time a char is written to the port, but
>>  we do need to know what was written so we could handle it on the
>>  guest.
>>
>> So it's talking about the serial console output, not input.
>>
>
> I'm talking about the real world.  Is any of this something that needs
> optimization?

Yes. See Sasha's other email. We should have mentioned that in the changelog.

> 1024 vcpus logging in via the serial console at 10Gbps.  Get real.

[...]

Huh, why are you bringing something like that up?

                                Pekka
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux