Re: [Libusbx-devel] [libusbx] persisting LIBUSB_ERROR_NO_MEM on burst condition

2012-12-11 Thread Tim Roberts
Mohamed HAMZAOUI wrote: > Solution, as pointed out Tim, is to buffer more data in a single > request. It's like nagle algorithm that I will implement, but I think > it is not a good solution in my case. > Firstly, there's several threads that send CAN frames in accordance > with specific conditions

Re: [Libusbx-devel] [libusbx] persisting LIBUSB_ERROR_NO_MEM on burst condition

2012-12-11 Thread Mohamed HAMZAOUI
Hi, To summarize, the number of fds is limited to the size of the table, 256 elements at most, this is an estimate from Microsoft that is enough! Solution, as pointed out Tim, is to buffer more data in a single request. It's like nagle algorithm that I will implement, but I think it is not a good

Re: [Libusbx-devel] [libusbx] persisting LIBUSB_ERROR_NO_MEM on burst condition

2012-12-11 Thread Orin Eman
On Mon, Dec 10, 2012 at 5:23 PM, Peter Stuge wrote: > Peter Stuge wrote: > > Are there considerations (timing? something else?) > > related to asking Windows for memory as needed > > Pete Batard wrote: > > Adding and testing array reallocation code is a PITA > > and development time is always sup