On Aug 9, 2005, at 5:50 PM, Prashant Alange wrote:
> ... I am linking multiple BDs only but
> no of BDs are very large in my case so I am allocating the memory and
> updating the BD pointer for all BDs.
I don't understand what you mean here.
> If i use mem= option as kernel command line arg
Thanks Dan for your explaination. I am linking multiple BDs only but
no of BDs are very large in my case so I am allocating the memory and
updating the BD pointer for all BDs. I am thinking of using mem start
parameter option. I even tried using __get_free_page instead of using
cpm_hostalloc() but
On Aug 9, 2005, at 10:57 AM, Prashant Alange wrote:
> Since the existing UART/ethernet drivers are using cpm_hostalloc() so
> I am also using the same function.
As I have said too many times before, cpm_hostalloc() is only used
to allocate small memory regions that would otherwise be wasteful
wi
On Aug 8, 2005, at 10:30 PM, Prashant Alange wrote:
> I am using alloc_bootmem_page() function to allocate memory required
> in my custom ethernet driver.
Why? Just use the normal Linux memory allocators.
> So I am thinking this could be because of cache since this
> driver is working fine on
Since the existing UART/ethernet drivers are using cpm_hostalloc() so
I am also using the same function. Then can I use kmalloc() to alloc
such huge memory. If at all I have to configure BATx to just test how
it behaves. How/where to configure BATx. One more thing is that
totally I am allocating ab
Hi all,
I am using alloc_bootmem_page() function to allocate memory required
in my custom ethernet driver . This driver reads buffer descriptors &
data from the memory allocated by bootmem page. This memory is updated
by CPM module. I am experiencing reliability issues with this driver.
It works f
