On 2015年03月02日 19:03, Horia Geantă wrote:
On 2/28/2015 8:00 AM, yanjiang@windriver.com wrote:
From: Yanjiang Jin
This can make sure we get a clean memory, else system would report
the below warning:
I'd avoid using kzalloc, it's an overhead on the hot path. kmalloc can
be used with a
On 2/28/2015 8:00 AM, yanjiang@windriver.com wrote:
> From: Yanjiang Jin
>
> This can make sure we get a clean memory, else system would report
> the below warning:
I'd avoid using kzalloc, it's an overhead on the hot path. kmalloc can
be used with a bit of attention to detail, i.e. what
On 2015年03月02日 19:03, Horia Geantă wrote:
On 2/28/2015 8:00 AM, yanjiang@windriver.com wrote:
From: Yanjiang Jin yanjiang@windriver.com
This can make sure we get a clean memory, else system would report
the below warning:
I'd avoid using kzalloc, it's an overhead on the hot path.
On 2/28/2015 8:00 AM, yanjiang@windriver.com wrote:
From: Yanjiang Jin yanjiang@windriver.com
This can make sure we get a clean memory, else system would report
the below warning:
I'd avoid using kzalloc, it's an overhead on the hot path. kmalloc can
be used with a bit of attention
From: Yanjiang Jin
This can make sure we get a clean memory, else system would report
the below warning:
caam_jr ffe301000.jr: DMA-API: device driver tries to free DMA memory it has
not allocated [device address=0xdeadbeefdeadbeef] [size=18446744073150512879
bytes]
[ cut here
From: Yanjiang Jin yanjiang@windriver.com
This can make sure we get a clean memory, else system would report
the below warning:
caam_jr ffe301000.jr: DMA-API: device driver tries to free DMA memory it has
not allocated [device address=0xdeadbeefdeadbeef] [size=18446744073150512879
bytes]
6 matches
Mail list logo