unsubscribing from freebsd lists (was "Re: contiguous memory allocation problem")

2006-12-01 Thread Garrett Cooper
Kamal R. Prasad wrote: Hello, I would like to unsubscribe myself from all freebsd mailing lists. I have sent an unsubscribe to freebsd-hackers-unsubscribe, but did not get any response to verify. Since the admin is on the mailing list, I would appreciate if you can delete my name and/or email me

Re: contiguous memory allocation problem

2006-11-30 Thread Kamal R. Prasad
Hello, I would like to unsubscribe myself from all freebsd mailing lists. I have sent an unsubscribe to freebsd-hackers-unsubscribe, but did not get any response to verify. Since the admin is on the mailing list, I would appreciate if you can delete my name and/or email me the procedure to follow

Re: contiguous memory allocation problem

2006-07-02 Thread Julian Elischer
Ian Dowse wrote: In message <[EMAIL PROTECTED]>, Hans Petter Selasky writes: But there is one problem, that has been overlooked, and that is High speed isochronous transfers, which are not supported by the existing USB system. I don't think that the EHCI specification was designed for scatt

Re: contiguous memory allocation problem

2006-07-02 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Hans Petter Selasky writes: >Ok. So the solution to my problem is to use scatter and gather. I will see >about updating my USB system to do it like that. > >But there is one thing I do not understand yet. When you load a page that >physically resides above 4GB, bec

Re: contiguous memory allocation problem

2006-07-02 Thread Hans Petter Selasky
On Sunday 02 July 2006 17:20, Ian Dowse wrote: > In message <[EMAIL PROTECTED]>, Ian Dowse writes: > >The trick is that if the 0x6000 bytes are contiguous in virtual > >memory then they never span more than 6 pages so one iTD is enough. > > Sorry, I meant of course 6 page boundaries, which means no

Re: contiguous memory allocation problem

2006-07-02 Thread Steve Kargl
On Sun, Jul 02, 2006 at 09:00:07AM -0700, Randall Hyde wrote: > > - Original Message - > From: "Peter Jeremy" <[EMAIL PROTECTED]> > To: "Randall Hyde" <[EMAIL PROTECTED]> > Sent: Saturday, July 01, 2006 11:10 PM > Subject: Re: FLEX, was Re: Return value of malloc(0) > > The following com

Re: contiguous memory allocation problem

2006-07-02 Thread Randall Hyde
- Original Message - From: "Peter Jeremy" <[EMAIL PROTECTED]> To: "Randall Hyde" <[EMAIL PROTECTED]> Sent: Saturday, July 01, 2006 11:10 PM Subject: Re: FLEX, was Re: Return value of malloc(0) The following compiles without error: %{ typedef int YYSTYPE; typedef int YYLTYPE; /* ** Allo

Re: contiguous memory allocation problem

2006-07-02 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Ian Dowse writes: >The trick is that if the 0x6000 bytes are contiguous in virtual >memory then they never span more than 6 pages so one iTD is enough. Sorry, I meant of course 6 page boundaries, which means no more than 7 pages. This is why the 7 physical address s

Re: contiguous memory allocation problem

2006-07-02 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Hans Petter Selasky writes: >On Sunday 02 July 2006 14:05, Ian Dowse wrote: >> This data structure requires the associated data buffer to be >> contiguous (relative to virtual memory), but allows the physical >> memory pages to be non-contiguous. Seven page poi

Re: contiguous memory allocation problem

2006-07-02 Thread Hans Petter Selasky
On Sunday 02 July 2006 14:05, Ian Dowse wrote: > In message <[EMAIL PROTECTED]>, Hans Petter Selasky writes: > >But there is one problem, that has been overlooked, and that is High speed > >isochronous transfers, which are not supported by the existing USB system. > > I don't think that the EHCI s

Re: contiguous memory allocation problem

2006-07-02 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Hans Petter Selasky writes: >But there is one problem, that has been overlooked, and that is High speed >isochronous transfers, which are not supported by the existing USB system. I >don't think that the EHCI specification was designed for scatter and gather, >whe

Re: contiguous memory allocation problem

2006-07-02 Thread Hans Petter Selasky
On Saturday 01 July 2006 21:44, David Malone wrote: > On Sat, Jul 01, 2006 at 10:44:54AM +0200, Hans Petter Selasky wrote: > > > The latest concensus seems to be that the USB system should make use of > > > the scatter-gather facilities in the hardware to avoid the need to > > > allocate large cont

Re: contiguous memory allocation problem

2006-07-01 Thread David Malone
On Sat, Jul 01, 2006 at 10:44:54AM +0200, Hans Petter Selasky wrote: > > The latest concensus seems to be that the USB system should make use of > > the scatter-gather facilities in the hardware to avoid the need to > > allocate large contiguous memory chunks. iedowse@ had mostly finished > > impl

Re: contiguous memory allocation problem

2006-07-01 Thread Peter Jeremy
On Sat, 2006-Jul-01 10:44:54 +0200, Hans Petter Selasky wrote: >Yes, but scatter and gather will add extra complexity to the driver, and maybe >an extra memory copy in most cases. The idea is to allocate less than or >equal to a page of memory, and then avoid the problem? The idea is to allocate

Re: contiguous memory allocation problem

2006-07-01 Thread Hans Petter Selasky
On Saturday 01 July 2006 14:34, Peter Jeremy wrote: > On Sat, 2006-Jul-01 10:44:54 +0200, Hans Petter Selasky wrote: > >Yes, but scatter and gather will add extra complexity to the driver, and > > maybe an extra memory copy in most cases. The idea is to allocate less > > than or equal to a page of

Re: contiguous memory allocation problem

2006-07-01 Thread Hans Petter Selasky
On Friday 30 June 2006 22:32, Peter Jeremy wrote: > On Fri, 2006-Jun-30 20:29:28 +0200, Hans Petter Selasky wrote: > >I sometimes see that the USB driver is unable to allocate contiguous > > memory for itself. For example I noticed that FreeBSD was unable to > > allocate 350kbytes of contiguous mem

Re: contiguous memory allocation problem

2006-06-30 Thread Peter Jeremy
On Fri, 2006-Jun-30 20:29:28 +0200, Hans Petter Selasky wrote: >I sometimes see that the USB driver is unable to allocate contiguous memory >for itself. For example I noticed that FreeBSD was unable to allocate >350kbytes of contiguous memory after that I had run "konqueror", the KDE web >browse

Re: contiguous memory allocation problem

2006-06-30 Thread Kip Macy
FreeBSD's strategy for doing page coloring makes contiguous memory allocation much past boot quite difficult. This will change when generalized superpage support is brought in (I hope in the near future). -Kip On 6/30/06, Hans Petter Selasky <[EMAIL PROTECTED]> wrote: Hi, I sometimes see tha

contiguous memory allocation problem

2006-06-30 Thread Hans Petter Selasky
Hi, I sometimes see that the USB driver is unable to allocate contiguous memory for itself. For example I noticed that FreeBSD was unable to allocate 350kbytes of contiguous memory after that I had run "konqueror", the KDE web browser and various other memory consuming applications for a while.