> -Original Message-
> From: kernelnewbies-boun...@kernelnewbies.org [mailto:kernelnewbies-
> boun...@kernelnewbies.org] On Behalf Of João Eduardo Luís
> Sent: Friday, June 03, 2011 12:40 PM
> To: Amirali Shambayati
> Cc: kernelnewbies
> Subject: Re: kernel memory allocation
>
> Hi.
>
> I
Hello,
Once again, I would pretty much enjoy if you CC'ed the list on replies.
On Jun 3, 2011, at 8:49 PM, Amirali Shambayati wrote:
> I set breakpoint before kmalloc. panic happens after kmalloc.
>
>> 2011/6/4 Amirali Shambayati
>> ofcourse it's null before allocate it. I make an instantiati
Hi.
In future replies, please CC the list.
Does it panic in during the kmalloc, or afterwards? Are you checking if
'newBun' is NULL?
I may be missing something obvious in that code, but unless you are out of
memory or with some past corruption, I don't think that should panic the kernel.
In a
Hi.
From [1] I'm lead to believe the only difference between the regular kmalloc()
arguments and those of kmalloc_node() is the one specifying which node you want
to allocate the memory on.
Aside from the third argument, which seems to be related with NUMA (with which
I never worked on kernel-
Hello all,
I just want to allocate memory for a struct instantiation. Would anyone
guide me what arguments I should pass to "kmalloc_node"?
Regards,
--
Amirali Shambayati
Bachelor Student
Computer Engineering Department
Sharif University of Technology
Tehran, Iran
Hello,
I wanted to know how much kernel and userspace memory is available on the
Linux system during run-time either by some C code or some procfile.
Do you know how to do that?
Thanks,
Dev
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
