Hi,
In 2.2 kernel do we really need its own LDT (not default_ldt) for every
process (no mm sharing) ??
In what circumstances a process may need its own LDT ??
--
Amol
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
I was talking about this leak 2 days back but my mail ot lost..
we have in vfree -->
vmfree_area_pages (calling) free_area_pmd (calling) free_area_pte (calling)
free_page.
The final free_page frees all the pages that are allocated to a memory region in
vmalloc.
Now where are we freeing
I was talking about this leak 2 days back but my mail ot lost..
we have in vfree --
vmfree_area_pages (calling) free_area_pmd (calling) free_area_pte (calling)
free_page.
The final free_page frees all the pages that are allocated to a memory region in
vmalloc.
Now where are we freeing
Hi,
In 2.2 kernel do we really need its own LDT (not default_ldt) for every
process (no mm sharing) ??
In what circumstances a process may need its own LDT ??
--
Amol
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
we have in vfree -->
vmfree_area_pages (calling) free_area_pmd (calling) free_area_pte (calling)
free_page.
The final free_page frees all the pages that are allocated to a memory region in
vmalloc.
Now where are we freeing pages that are allocated to page table themselves.
For simplicity we can
we have in vfree --
vmfree_area_pages (calling) free_area_pmd (calling) free_area_pte (calling)
free_page.
The final free_page frees all the pages that are allocated to a memory region in
vmalloc.
Now where are we freeing pages that are allocated to page table themselves.
For simplicity we can
well... I doubt whether buddy allocator would take u to a situation where pages
0 and 2 are used and 1 and 3 are free...
try reading __get_free_pages in mm/page_alloc.c
[EMAIL PROTECTED] on 06/15/2001 12:39:20 AM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Subject: Buddy System
well... I doubt whether buddy allocator would take u to a situation where pages
0 and 2 are used and 1 and 3 are free...
try reading __get_free_pages in mm/page_alloc.c
[EMAIL PROTECTED] on 06/15/2001 12:39:20 AM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Subject: Buddy System
Hi,
I was unable to understand the logic of the following sanity checks in
slab.c/kmem_cache_init ().
if (kmem_cache_diff(c_firstp,c_magic) != kmem_slab_diff(s_nextp,s_magic) ||
kmem_cache_diff(c_firstp,c_inuse) != kmem_slab_diff(s_nextp,s_inuse) ||
kmem_cache_offset(c_lastp) - ((unsigned
Hi,
I was unable to understand the logic of the following sanity checks in
slab.c/kmem_cache_init ().
if (kmem_cache_diff(c_firstp,c_magic) != kmem_slab_diff(s_nextp,s_magic) ||
kmem_cache_diff(c_firstp,c_inuse) != kmem_slab_diff(s_nextp,s_inuse) ||
kmem_cache_offset(c_lastp) - ((unsigned
Hi,
The question may sound very stupid... But I have following doubt.
suppose I am making some change in sched.c and now I want to build my kernel
that reflects the change..
Is there any way I can avoid answering all the questions when I do make zImage ?
In short how should I compile the
Hi,
The question may sound very stupid... But I have following doubt.
suppose I am making some change in sched.c and now I want to build my kernel
that reflects the change..
Is there any way I can avoid answering all the questions when I do make zImage ?
In short how should I compile the
Hi Xiong,
you can get a lot of books on kernel internals... But my experience says...
reading code is the best solutionall the intricacies can only be cleared
when u hack the code
btw a new "understanding the linux kernel" by O'reilly pub. can be helpful in
'code reading'.
Amol
well... the book sounds good...
but... I am still thinking... what it has to do with linux kernel ??
[EMAIL PROTECTED] on 04/24/2001 04:27:56 PM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Subject: Greetings!
1 in 6 children are victimized before the age of 16.
Hello, my
It may be possible that this is not the good choice...
but u can try ... schedule_timeout(timeout) function see kernel/sched.c for
more details about this function
Amol
Rajeev Nigam <[EMAIL PROTECTED]> on 04/24/2001 03:29:04 PM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Hi,
I want to look into this problem. Its seems to be very interesting. But I
was not following the thread from the beginning (and I mistakely deleted all
these mails :( .. ).. I hope you won't mind answering following questions...
1) you are doing this on an MP or a uniprocessor ?
2)
Rajeev Nigam <[EMAIL PROTECTED]> on 04/24/2001 03:29:04 PM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Subject: Delay Function
What function i have to use to put a delay in a driver at kernel mode
between reading from and writing to com port.
Looking forward for ur help.
Hi,
I want to look into this problem. Its seems to be very interesting. But I
was not following the thread from the beginning (and I mistakely deleted all
these mails :( .. ).. I hope you won't mind answering following questions...
1) you are doing this on an MP or a uniprocessor ?
2) I
Hi,
I want to look into this problem. Its seems to be very interesting. But I
was not following the thread from the beginning (and I mistakely deleted all
these mails :( .. ).. I hope you won't mind answering following questions...
1) you are doing this on an MP or a uniprocessor ?
2) I
Rajeev Nigam [EMAIL PROTECTED] on 04/24/2001 03:29:04 PM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Subject: Delay Function
What function i have to use to put a delay in a driver at kernel mode
between reading from and writing to com port.
Looking forward for ur help.
It may be possible that this is not the good choice...
but u can try ... schedule_timeout(timeout) function see kernel/sched.c for
more details about this function
Amol
Rajeev Nigam [EMAIL PROTECTED] on 04/24/2001 03:29:04 PM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Hi,
I want to look into this problem. Its seems to be very interesting. But I
was not following the thread from the beginning (and I mistakely deleted all
these mails :( .. ).. I hope you won't mind answering following questions...
1) you are doing this on an MP or a uniprocessor ?
2)
well... the book sounds good...
but... I am still thinking... what it has to do with linux kernel ??
[EMAIL PROTECTED] on 04/24/2001 04:27:56 PM
To: [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Subject: Greetings!
1 in 6 children are victimized before the age of 16.
Hello, my
Erik Paulson <[EMAIL PROTECTED]> on 04/24/2001 01:14:27 AM
To: Christian Ehrhardt <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: Re: BUG: Global FPU corruption in 2.2
On 23 Apr 2001 18:11:48 +0200, Christian Ehrhardt wrote:
> On Thu,
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi,
In update_wall_one_tick() function, we have following
xtime.tv_usec += tick + time_adjust_step.
where tick = (100 + hz/2)/hz.
In systems where we have TSC why we cannot use that to update xtime.tv_usec. It
should give better time estimate. and the values that are
Hi,
In update_wall_one_tick() function, we have following
xtime.tv_usec += tick + time_adjust_step.
where tick = (100 + hz/2)/hz.
In systems where we have TSC why we cannot use that to update xtime.tv_usec. It
should give better time estimate. and the values that are
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Erik Paulson [EMAIL PROTECTED] on 04/24/2001 01:14:27 AM
To: Christian Ehrhardt [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: Re: BUG: Global FPU corruption in 2.2
On 23 Apr 2001 18:11:48 +0200, Christian Ehrhardt wrote:
On Thu, Apr 19,
Kurt Roeckx <[EMAIL PROTECTED]> on 04/11/2001 06:16:52 AM
To: Miquel van Smoorenburg <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: Re: Let init know user wants to shutdown
On Wed, Apr 11, 2001 at 01:38:30AM +0200, Kurt Roeckx wrote:
> On Tue, Apr 10,
Kurt Roeckx [EMAIL PROTECTED] on 04/11/2001 06:16:52 AM
To: Miquel van Smoorenburg [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: Re: Let init know user wants to shutdown
On Wed, Apr 11, 2001 at 01:38:30AM +0200, Kurt Roeckx wrote:
On Tue, Apr 10, 2001 at
Jamie Lokier <[EMAIL PROTECTED]> on 04/06/2001 03:18:13 PM
To: Amol Lad/HSS@HSS
cc: [EMAIL PROTECTED]
Subject: Re: __switch_to macro
[EMAIL PROTECTED] wrote:
> 1) What exactly is meant by ' stale segment register values' in the note.
> 2) In the above macro, I think we recover
Hi,
The note above __switch_to macro in i386/kernel/process.c says that we no
more use hardware context switching as some problems in recovering from
saved state that is no longer valid. (I am peeking into 2.2 kernel). Now I have
following questions
1) What exactly is meant by ' stale
Hi,
The note above __switch_to macro in i386/kernel/process.c says that we no
more use hardware context switching as some problems in recovering from
saved state that is no longer valid. (I am peeking into 2.2 kernel). Now I have
following questions
1) What exactly is meant by ' stale
Jamie Lokier [EMAIL PROTECTED] on 04/06/2001 03:18:13 PM
To: Amol Lad/HSS@HSS
cc: [EMAIL PROTECTED]
Subject: Re: __switch_to macro
[EMAIL PROTECTED] wrote:
1) What exactly is meant by ' stale segment register values' in the note.
2) In the above macro, I think we recover
This concept I think is used in Solaris .. as they have dynamic loadable
schedulers..
Zdenek Kabelac <[EMAIL PROTECTED]> on 04/05/2001 05:43:15 PM
To: Andrea Arcangeli <[EMAIL PROTECTED]>
cc:(bcc: Amol Lad/HSS)
Subject: Re: [Lse-tech] Re: a quest for a better scheduler
Hello
"Heusden, Folkert van" <[EMAIL PROTECTED]> on 04/05/2001 03:45:13 PM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: RE: random PIDs
> Finished & tested my random PID kernel/fork.c:get_pid() replacement.
> > This one keeps track of the last N (default
well..don't fire me for asking such a stupid question... I am new to linux
kernel world...
I want to know the release naming conventions in linux..
I know the following...
2.1.xx --> means developmet release
2.2.xx --> means stable release...
Now what 2.2.xx-pre6 or 2.2.xx-ac3 means ??
Amol
"Heusden, Folkert van" [EMAIL PROTECTED] on 04/05/2001 03:45:13 PM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: RE: random PIDs
Finished tested my random PID kernel/fork.c:get_pid() replacement.
This one keeps track of the last N (default is 64)
This concept I think is used in Solaris .. as they have dynamic loadable
schedulers..
Zdenek Kabelac [EMAIL PROTECTED] on 04/05/2001 05:43:15 PM
To: Andrea Arcangeli [EMAIL PROTECTED]
cc:(bcc: Amol Lad/HSS)
Subject: Re: [Lse-tech] Re: a quest for a better scheduler
Hello
Just
In 2.4 kernel we now have no limit on the number of tasks running on a system
(no NR_TASKS anymore)...
I was just wondering on the efficiency of get_pid() implemetation... Although
'next_safe' concept in this function seems useful but I think we now need a
robust PID allocator..
We can have a
If we are facing these problems for "normal case" then hope the Solaris is
handling it !!
Amol
Fabio Riccardi <[EMAIL PROTECTED]> on 04/04/2001 07:03:57 AM
To: Alan Cox <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: Re: a quest for a better scheduler
If we are facing these problems for "normal case" then hope the Solaris is
handling it !!
Amol
Fabio Riccardi [EMAIL PROTECTED] on 04/04/2001 07:03:57 AM
To: Alan Cox [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Amol Lad/HSS)
Subject: Re: a quest for a better scheduler
Alan,
In 2.4 kernel we now have no limit on the number of tasks running on a system
(no NR_TASKS anymore)...
I was just wondering on the efficiency of get_pid() implemetation... Although
'next_safe' concept in this function seems useful but I think we now need a
robust PID allocator..
We can have a
44 matches
Mail list logo
