mlockall() with MCL_FUTURE

From: Amol Kumar Lad (amolk@ishoni.com)
Date: Tue Oct 29 2002 - 20:11:46 EST

Next message: Jaroslav Kysela: "[PATCH] MODULE_DEVICE_TABLE update && !CONFIG_PROC_FS"
Previous message: Jens Axboe: "Re: [PATCH] Fix: BK-Current doesn't compile w/o SCSI enabled"
Next in thread: Tom Rini: "Re: mlockall() with MCL_FUTURE"
Reply: Tom Rini: "Re: mlockall() with MCL_FUTURE"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,
I was just going through its implementation. If mlockall() is invoked
with MCL_FUTURE, does it mean that all the existing locked mappings of
process should get unlocked ? Attaching code segment from do_mlockall().
I am using 2.4.18 kernel

static int do_mlockall(int flags)
{
   ...
                newflags = vma->vm_flags | VM_LOCKED;
                if (!(flags & MCL_CURRENT))
                        newflags &= ~VM_LOCKED;
                error = mlock_fixup(vma, vma->vm_start, vma->vm_end,
newflags);
   ...
}

please cc me.

thanks
Amol

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Jaroslav Kysela: "[PATCH] MODULE_DEVICE_TABLE update && !CONFIG_PROC_FS"
Previous message: Jens Axboe: "Re: [PATCH] Fix: BK-Current doesn't compile w/o SCSI enabled"
Next in thread: Tom Rini: "Re: mlockall() with MCL_FUTURE"
Reply: Tom Rini: "Re: mlockall() with MCL_FUTURE"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:42 EST