[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BADF286A08026E4DAFA9622608E3D8DB063CE258A1@rosser.pointgrey.local>
Date: Mon, 7 Nov 2011 12:13:05 -0800
From: Tim Vlaar <Tvlaar@...rey.com>
To: Alan Stern <stern@...land.harvard.edu>
CC: Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
Greg KH <greg@...ah.com>,
Markus Rechberger <mrechberger@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
USB list <linux-usb@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: RE: [Patch] Increase USBFS Bulk Transfer size
Having a setting that we could adjust or even set to "no limit" would work for us :)
Thanks
Tim
-----Original Message-----
From: Alan Stern [mailto:stern@...land.harvard.edu]
Sent: Monday, November 07, 2011 11:56 AM
To: Tim Vlaar
Cc: Sarah Sharp; Greg KH; Markus Rechberger; Alan Cox; USB list; LKML
Subject: RE: [Patch] Increase USBFS Bulk Transfer size
On Mon, 7 Nov 2011, Tim Vlaar wrote:
> Hi Sarah,
>
> One of our cameras can produce 60MB images. We usually queue up 10
> images. In Windows we have had customers queue up 100s of images at
> 2-3MB/image, but not at 60MB at a time ... yet. That could easily
> amount to 60x10 = 600MB of in flight data or more. Should there be a
> limit as long as there is memory available?
This is debatable. There are limits on how much memory a single process can allocate, but those limits don't apply to usbfs. Even the patch Sarah referred to doesn't impose a per-process limit, but rather an overall global limit.
If we make the usbfs limit adjustable, one of the settings could be "no limit". Then nothing would prevent you from using up more and more memory for your USB transfers until the machine runs out. :-)
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists