All of lore.kernel.org
 help / color / mirror / Atom feed
From: harry <harry@hebutterworth.freeserve.co.uk>
To: xen-devel@lists.xensource.com
Subject: USB virt 2.6 split driver patch series
Date: Mon, 21 Nov 2005 13:18:24 +0000	[thread overview]
Message-ID: <1132579104.31295.110.camel@localhost.localdomain> (raw)

I'm about to post a series of 17 patches which implement the xenidc
interdomain communications code and the USB split driver built on the
xenidc code.

These patches have been tested against today's unstable for the i386
build and can be successfully used to create a filesystem on and mount a
USB key.

Currently the code requires swiotlb=force and there are a few issues
which need to be addressed:

o - The USB protocol requires stalling the URB queue during error
conditions.  This isn't done correctly yet which makes the code unsafe
for write access during error recovery.  The 2.4 code had this problem
as well I only discovered it recently.

o - The USB-specific part of the interdomain protocol is using polling
for device discovery which is inefficient.  This is the same strategy as
the 2.4 code.

o - The resource pools are currently only allocating the minimum
resources required to avoid deadlock so performance will be resource
constrained.  This can be fixed either by implementing a larger static
resource allocation or improving the buffer_resource_provider to
implement a dynamic shared resource pool.  Either is fairly easy.

o - I've reformatted all the code to the kernel coding style using
Lindent and not attempted to improve it after that.  Some of the
formatting needs to be improved.

Now that it's basically working, if possible, I'd like to get the code
into the tree and work on it there.

Any feedback on the patches, particularly on what it's going to take to
get the code into the tree, would be most welcome.

Harry.

             reply	other threads:[~2005-11-21 13:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 13:18 harry [this message]
2005-11-21 13:49 ` USB virt 2.6 split driver patch series Vincent Hanquez
2005-11-21 14:01   ` harry
2005-11-21 14:27     ` Vincent Hanquez
2005-11-21 14:29     ` Dave Feustel
2005-11-21 14:41     ` NAHieu
2005-11-21 15:14       ` harry
2005-11-21 15:27         ` NAHieu
2005-11-21 15:39           ` harry
2005-11-21 17:02             ` NAHieu
2005-11-21 17:17               ` harry
2005-11-22  1:59                 ` NAHieu
2005-11-22  2:00                   ` NAHieu
2005-11-22 10:24                     ` harry
2005-11-22 11:07                       ` Vincent Hanquez
2005-11-22 15:37                         ` Anthony Liguori
2005-11-22 20:27                           ` Vincent Hanquez
2005-11-21 15:44         ` Muli Ben-Yehuda
2005-11-21 18:49           ` Harry Butterworth
2005-11-21 18:58             ` Muli Ben-Yehuda
2005-11-25 19:16           ` harry
2005-11-21 17:26     ` Oleg Goldshmidt
2005-11-21 15:34       ` harry
2005-11-21 14:25   ` Dave Feustel
2005-11-21 14:36     ` Vincent Hanquez
2005-11-21 15:24       ` Dave Feustel
2005-11-21 16:03         ` Vincent Hanquez
2005-11-21 16:30           ` Dave Feustel

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=1132579104.31295.110.camel@localhost.localdomain \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=xen-devel@lists.xensource.com \
    /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.