From: "David S. Ahern" <daahern@cisco.com>
To: Alexander Graf <agraf@suse.de>
Cc: Jan Kiszka <jan.kiszka@web.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: ehci update
Date: Tue, 13 Apr 2010 21:35:50 -0600 [thread overview]
Message-ID: <4BC53816.8060401@cisco.com> (raw)
In-Reply-To: <73AB16E6-5B01-4848-B8B7-895AEC5DAF76@suse.de>
On 04/13/2010 07:20 PM, Alexander Graf wrote:
>>>> It still needs a lot of love, but definitely an improvement from the
>>>> last version. The biggest difference for the performance boost and
>>>> stability is discovering that the usbfs in linux limits transactions to
>>>> 16k versus the EHCI spec which allows 20k per qTD. I added a hack to
>>>> submit which detects 20k requests from a guest and breaks it up into 2
>>>> requests through the host (a 16k and then a 4k).
>>>
>>> Did someone already bring this up on LKML or wherever usbfs is
>>> discussed? Should be fixable, I naively guess.
>>
>> I submitted the patch to linux-usb and it was nack'ed. The response was
>> that memory is allocated in powers of 2 so trying to up the limit from
>> 16k to 20k means it will actually want to find 32k of contiguous memory.
>> The suggestion was to handle it with multiple requests within qemu. I
>> guess libusb does that.
>
> Any reason we're not using libusb?
Good question. I was wondering the same. I was going to look at
converting usb-linux to use libusb1 when I get some time.
David
>
>
> Alex
>
next prev parent reply other threads:[~2010-04-14 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 4:33 [Qemu-devel] ehci update David S. Ahern
2010-04-13 23:35 ` [Qemu-devel] " Jan Kiszka
2010-04-13 23:50 ` David S. Ahern
2010-04-14 1:20 ` Alexander Graf
2010-04-14 3:35 ` David S. Ahern [this message]
2010-04-14 19:38 ` Jan Kiszka
2010-04-14 19:48 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC53816.8060401@cisco.com \
--to=daahern@cisco.com \
--cc=agraf@suse.de \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.