From: Duncan Sands <baldrick@free.fr>
To: "René Rebe" <rene@exactcode.de>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: MAX_USBFS_BUFFER_SIZE
Date: Wed, 1 Mar 2006 22:59:26 +0100 [thread overview]
Message-ID: <200603012259.26790.baldrick@free.fr> (raw)
In-Reply-To: <200603012242.35633.rene@exactcode.de>
> So, queing alot URBs is the recommended way to sustain the bus? Allowing
> way bigger buffers will not be realistic?
usbfs could copy the user buffer to a bunch of non-contiguous pages, and
then fire those off in an urb using the scatter-gather stuff. [Rather than,
as now, allocating a bunch of contiguous pages using kmalloc]. That would
probably make it possible to use much much bigger user-space buffers. Plus
the code looks rather easy to write.
Ciao,
Duncan.
next prev parent reply other threads:[~2006-03-03 8:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 20:16 MAX_USBFS_BUFFER_SIZE René Rebe
2006-03-01 20:53 ` MAX_USBFS_BUFFER_SIZE Oliver Neukum
2006-03-01 21:32 ` MAX_USBFS_BUFFER_SIZE Greg KH
2006-03-01 21:42 ` MAX_USBFS_BUFFER_SIZE René Rebe
2006-03-01 21:54 ` MAX_USBFS_BUFFER_SIZE Greg KH
2006-03-01 22:34 ` MAX_USBFS_BUFFER_SIZE Olivier Galibert
2006-03-01 22:41 ` MAX_USBFS_BUFFER_SIZE Greg KH
2006-03-01 23:25 ` MAX_USBFS_BUFFER_SIZE Olivier Galibert
2006-03-01 23:37 ` MAX_USBFS_BUFFER_SIZE Greg KH
2006-03-02 9:04 ` MAX_USBFS_BUFFER_SIZE René Rebe
2006-03-02 16:47 ` MAX_USBFS_BUFFER_SIZE Greg KH
2006-03-02 16:03 ` MAX_USBFS_BUFFER_SIZE René Rebe
2006-03-02 16:47 ` MAX_USBFS_BUFFER_SIZE Greg KH
2006-03-01 21:59 ` Duncan Sands [this message]
2006-03-03 10:34 ` MAX_USBFS_BUFFER_SIZE Oliver Neukum
[not found] ` <mailman.1141249502.22706.linux-kernel2news@redhat.com>
2006-03-02 21:05 ` MAX_USBFS_BUFFER_SIZE Pete Zaitcev
2006-03-03 7:27 ` MAX_USBFS_BUFFER_SIZE René Rebe
2006-03-03 20:32 ` MAX_USBFS_BUFFER_SIZE Greg KH
2006-03-03 8:12 ` MAX_USBFS_BUFFER_SIZE Duncan Sands
2006-03-03 10:29 ` MAX_USBFS_BUFFER_SIZE Oliver Neukum
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=200603012259.26790.baldrick@free.fr \
--to=baldrick@free.fr \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene@exactcode.de \
/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.