xiaohuidexinge :
> Hi guys:
> I am a Chinese. I 've join in this mailgroup for a while. But I find it
> hard to join in these discussion, because I am a newb for linux and my
> English is just at the beginning. So I want to find a partner to do some
> language exchange, that I help you i
Chauhan wrote:
> While going through vmscan.c, I found references to mem_cgroup. What
> kind of group is it? When is it used?
>
Documentation/cgroups/cgroups.txt
Documentation/cgroups/memory.txt
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecar...@nl.linu
Frédéric Weisbecker wrote:
> Ok thank you. I'm tring linux-next.
> Is there really an mm git tree? I can't find it, just see the patch on
> kernel.org
>
-mm is on top of linux-next.
You can get the -mm patch in http://www.kernel.org/
And you can get the latest -mm patches in
http://userweb.ker
Mulyadi Santosa wrote:
> Hi Li...
>
> On Wed, Jun 18, 2008 at 10:09 AM, Li Zefan <[EMAIL PROTECTED]> wrote:
>> Yes, it's something like CKRM. Some years ago we had several proposals like
>> CKRM,
>> ResGroups, User BeanCounters and others.
>
> Inte
Mulyadi Santosa wrote:
> Hi Li..
>
> On Wed, Jun 18, 2008 at 7:44 AM, Li Zefan <[EMAIL PROTECTED]> wrote:
>> Cgroup is still under development. And we have cpuset, cpu, cpuacct, memory
>> and
>> device subsystems, besides these we have memrlimit subsys in -mm
Peter Teoh wrote:
> I read this:
>
> http://lwn.net/Articles/236078/
>
> But still don't understand what is containers? what is the rational
> behind the concept? Which applications is it useful?
>
It renamed to cgroup before merging into mainline, and cgroup stands for control
group. Cgrou
pradeep singh wrote:
> Hi All,
>
> A Quick but perhaps dumbass query,
>
> 1. int function_A(...)
> {
> ...;
> }
>
> 2. int function_B(...)
> {
> ...;
> }
> EXPORT_SYMBOL(function_B);
>
> Okay i understand I should use the EXPORT_SYMBOL way if i want
> funct
debian developer wrote:
> Hello,
>
> Consider the following code snippet...
>
> const char *type;
>
> switch (rfkill->type) {
> case RFKILL_TYPE_WLAN:
> type = "wlan";
> break;
> case RFKILL_TYPE_BLUETOOTH:
> type =
Erik Mouw wrote:
> On Sat, Mar 29, 2008 at 04:03:18AM -0400, Robert P. J. Day wrote:
>> is there somewhere an actual quantification (is that a word?) to the
>> benefits of likely() and unlikely() in the kernel code? i've always
>> been curious about what difference those constructs made. thanks
Peter Teoh wrote:
> Further to my earlier statement that either init.h is wrong, or the source
> codes are not cleanup, my personal guess is that init.h is not correct (this
> line - "Also note, that this data cannot be "const".") This is because
> these __data can be either constant or non-c
Mulyadi Santosa wrote:
> Hi...
>
> Just trying to offer idea...
> On 2/1/08, Peter Teoh <[EMAIL PROTECTED]> wrote:
>> I was puzzled today, as several of machines all compiled the latest git
>> pulled kernel with the following errors:
>>
>>CHK include/linux/version.h
>>CHK include/l
Tang Rui wrote:
> Hi,
>
>Could anyone help me to analyse the following issue? I just
> understand that during atomic operation my driver might call some
> methods that can cause scheduling.
>
> I don't know where the problem is. Could anyone help me to figure it
> out?
>
It's not allow
Onkar 写道:
> let me tell the sequence of step I followed before I got that error :
>
> (1) I compiled the kernel with the CONFIG_B44=m option
> (2) then I booted with this new kernel 2.6.18
> (3) at his time lsmod |grep b44 showed b44 (that means module loaded at boot
> time)
> (4) then , I remove
sahlot arvind wrote:
> Recently I started looking into linux kernel and trying to understand the
> code.
> I am working with linux-2.6.9.
> in file include/llinux/list.h - I found something like this.
>
> #define INIT_LIST_HEAD(ptr) do { \
> (ptr)->next = (ptr); (ptr)->prev = (ptr); \
> }
sahlot arvind wrote:
> Yes I get an error in this code -
> -
> struct list_head {
> struct list_head *next, *prev;
> };
>
> #define INIT_LIST_HEAD(ptr){(ptr)->next = (ptr); (ptr)->prev = (ptr);}
>
> int main ()
> {
> int i;
> struct list_head mylist
venkatram ajmeera wrote:
> For Compilation of Linux-2.6.18 kernel
> I follwed these steps
>
> 1.Extracetd the source.
> 2.Copied it to home dir
> 3.Make mrproper
> 4.Make menuconfig
> 5.Make
> 6.Make modules_install
> 7.Make install
>
> UPTO these steps No errors occurred.
>
> After this I am
Sarath Kamisetty wrote:
> Hi,
>
> Are there any documents explaining the TCP/IP stack design and
> implementation in Linux ? What is a good place to start understanding
> Linux TCP/IP implementation ? Any pointers to the code will also be
> helpful.
>
Maybe this bo
17 matches
Mail list logo
