On Feb 6, 2008 11:19 AM, Rick Brown [EMAIL PROTECTED] wrote:
Hi,
I had read that the operating systems that use copy-on-write mechanism
for fork(), it is better if they deliberately allow the CHILD to run
first.
This would be better because in 99% of the cases child will call
exec() and
On Feb 6, 2008 6:03 PM, Rajat Jain [EMAIL PROTECTED] wrote:
Hi,
I had read that the operating systems that use copy-on-write
mechanism for fork(), it is better if they deliberately allow the
CHILD to run first.
This would be better because in 99% of the cases child will call
Hi,
I had read that the operating systems that use copy-on-write
mechanism for fork(), it is better if they deliberately allow the
CHILD to run first.
This would be better because in 99% of the cases child will call
exec() and the new address space will be allocated. Instead if the
I found one header file for x86 that implement the TLB flushing -
include/asm-x86/tlbflush.h (the different implementation are used are
used because of the diff generation of x86:
static inline void __native_flush_tlb(void)
{
write_cr3(read_cr3());
}
(my questions: WHAT IS THE DIFF
On Feb 6, 2008 7:54 PM, Peter Teoh [EMAIL PROTECTED] wrote:
I found one header file for x86 that implement the TLB flushing -
include/asm-x86/tlbflush.h (the different implementation are used are
used because of the diff generation of x86:
static inline void __native_flush_tlb(void)
{
I was reading http://linux-mm.org/PageAllocation, and came across this
arch-indep mm/page_alloc.c, there is a static function bad_page():
static void bad_page(struct page *page)
{
printk(KERN_EMERG Bad page state in process '%s'\n
KERN_EMERG page:%p flags:0x%0*lx
On Feb 5, 2008 11:42 PM, Mulyadi Santosa [EMAIL PROTECTED] wrote:
Hi...
On 2/6/08, Martin Candurra [EMAIL PROTECTED] wrote:
I had to get some data from a user process within a kernel module. That
process wasn't the current so the process pgd was not the same as the
current pgd (for this
Hi,
I had read that the operating systems that use copy-on-write mechanism
for fork(), it is better if they deliberately allow the CHILD to run
first.
This would be better because in 99% of the cases child will call
exec() and the new address space will be allocated. Instead if the
parent is
That's userspace tool.
# rpm -qf `whereis losetup`
util-linux-2.12a-16
regards,
Mulyadi.
Well thanks for the reply.
I actually wanted to know how does the /sbin/losetup command function, which
is what i am unable to find. I found the losetup.c in util-linux, but it
does not give me the
Hi,
static void bad_page(struct page *page)
{
printk(KERN_EMERG Bad page state in process '%s'\n
KERN_EMERG page:%p flags:0x%0*lx mapping:%p
mapcount:%d count:%d\n
KERN_EMERG Trying to fix it up, but a reboot is
needed\n KERN_EMERG
10 matches
Mail list logo