From: Johannes Erdfelt <johannes@erdfelt.com>
To: antirez <antirez@invece.org>
Cc: "Dunlap, Randy" <randy.dunlap@intel.com>,
Greg KH <greg@wirex.com>, Heitzso <xxh1@cdc.gov>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: USB broken in 2.4.0
Date: Fri, 5 Jan 2001 20:53:23 -0500 [thread overview]
Message-ID: <20010105205322.F8324@sventech.com> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDEBE@orsmsx31.jf.intel.com> <20010106045050.C1748@prosa.it>
In-Reply-To: <20010106045050.C1748@prosa.it>; from antirez on Sat, Jan 06, 2001 at 04:50:50AM +0100
On Sat, Jan 06, 2001, antirez <antirez@invece.org> wrote:
> On Fri, Jan 05, 2001 at 04:48:00PM -0800, Dunlap, Randy wrote:
> > This rings a small bell with me.
> > There was a change by Dan Streetman IIRC to limit
> > usbdevfs bulk transfers to PAGE_SIZE (4 KB for x86,
> > or 0x1000). Anything larger than that returns
> > an error (-EINVAL).
>
> Yes, devio.c, proc_bulk():
>
> if (len1 > PAGE_SIZE)
> return -EINVAL;
>
> Actually it is the max transfer size I can reach.
> I guess that to limit the page size can be an impementation
> advantage but it may slow-down a bit some userspace driver.
> I feel that even if the linux way is to implement the USB
> drivers in kernel space a full-featured USB user space access
> should be allowed.
This is the responsibility of the user space access. Using 4k reads
versus 8k reads won't increase performance (noticably), or will it
function any more correctly.
The next version of libusb will split up reads correctly so applications
using the library don't need to worry about this.
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-06 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 0:48 USB broken in 2.4.0 Dunlap, Randy
2001-01-06 3:50 ` antirez
2001-01-06 1:53 ` Johannes Erdfelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:38 Heitzso
2001-01-08 17:54 ` antirez
2001-01-05 17:38 Heitzso
2001-01-05 18:00 ` Greg KH
2001-01-05 23:04 ` antirez
2001-01-06 2:39 ` antirez
2001-01-06 3:40 ` antirez
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=20010105205322.F8324@sventech.com \
--to=johannes@erdfelt.com \
--cc=antirez@invece.org \
--cc=greg@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@intel.com \
--cc=xxh1@cdc.gov \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox