Re: one usb_mem pool per host controller

2012-03-15 Thread Tobias Ulmer
On Thu, Mar 15, 2012 at 08:29:08PM +0100, Mark Kettenis wrote: > > Date: Wed, 14 Mar 2012 02:25:02 +0100 > > From: Tobias Ulmer > > > > I have a couple of machines with an EHCI controller that refuses to work > > with memory above 2G, causing all kinds of trouble. This diff enables > > setting a

Re: one usb_mem pool per host controller

2012-03-15 Thread Mark Kettenis
> Date: Wed, 14 Mar 2012 02:25:02 +0100 > From: Tobias Ulmer > > I have a couple of machines with an EHCI controller that refuses to work > with memory above 2G, causing all kinds of trouble. This diff enables > setting a bus_dma boundary and allows me to make off-site backups again. Setting the

Re: one usb_mem pool per host controller

2012-03-14 Thread Tobias Ulmer
On Tue, Mar 13, 2012 at 10:59:36PM -0400, Ted Unangst wrote: > I don't think it's necessary to allocate this structure. Just stick > it in usbd_bus entirely. > Alright, the intention was not to add another struct to the usb_mem header, but I don't feel strongly about it. The feedback so far ind

Re: one usb_mem pool per host controller

2012-03-13 Thread Ted Unangst
On Wed, Mar 14, 2012, Tobias Ulmer wrote: > I have a couple of machines with an EHCI controller that refuses to work > with memory above 2G, causing all kinds of trouble. This diff enables > setting a bus_dma boundary and allows me to make off-site backups again. > > Due to the bus_dma pool being

one usb_mem pool per host controller

2012-03-13 Thread Tobias Ulmer
I have a couple of machines with an EHCI controller that refuses to work with memory above 2G, causing all kinds of trouble. This diff enables setting a bus_dma boundary and allows me to make off-site backups again. Due to the bus_dma pool being shared across all HCs, it was necessary to pull the