From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>
Subject: Re: [RFC PATCH for -mm 3/5] kill unnecessary locked_vm adjustment
Date: Tue, 12 Aug 2008 15:55:10 -0400 [thread overview]
Message-ID: <1218570910.6360.120.camel@lts-notebook> (raw)
In-Reply-To: <20080811160542.945F.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Mon, 2008-08-11 at 16:06 +0900, KOSAKI Motohiro wrote:
> Now, __mlock_vma_pages_range never return positive value.
> So, locked_vm adjustment code is unnecessary.
True, __mlock_vma_pages_range() does not return a positive value. [It
didn't before this patch series, right?] However, you are now counting
mlocked hugetlb pages and user mapped kernel pages against locked_vm--at
least in the mmap(MAP_LOCKED) path--even tho' we don't actually mlock().
Note that mlock[all]() will still avoid counting these pages in
mlock_fixup(), as I think it should.
Huge shm pages are already counted against user->locked_shm. This patch
counts them against mm->locked_vm, as well, if one mlock()s them. But,
since locked_vm and locked_shm are compared to the memlock rlimit
independently, so we won't be double counting the huge pages against
either limit. However, mlock()ed [not SHMLOCKed] hugetlb pages will
now be counted against locked_vm limit and will reduce the amount of
non-shm memory that the task can lock [maybe not such a bad thing?].
Also, mlock()ed hugetlb pages will be included in the /proc/<pid>/status
"VmLck" element, even tho' they're not really mlocked and they don't
show up in the /proc/meminfo "Mlocked" count.
Similarly, mlock()ing a vm range backed by kernel pages--e.g.,
VM_RESERVED|VM_DONTEXPAND vmas--will show up in the VmLck status
element, but won't actually be mlocked nor counted in Mlocked meminfo
field. They will be counted against the task's locked vm limit.
So, I don't know whether to Ack or Nack this. I guess it's no further
from reality than the current code. But, I don't think you need this
one. The code already differentiates between negative values as error
codes and non-negative values as an adjustment to locked_vm, so you
should be able to meet the standards mandated error returns without this
patch.
Still thinking about this...
Lee
>
> also, related comment fixed.
>
>
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>
> ---
> mm/mlock.c | 18 +++++-------------
> mm/mmap.c | 10 +++++-----
> 2 files changed, 10 insertions(+), 18 deletions(-)
>
> Index: b/mm/mlock.c
> ===================================================================
> --- a/mm/mlock.c
> +++ b/mm/mlock.c
> @@ -276,7 +276,7 @@ int mlock_vma_pages_range(struct vm_area
> unsigned long start, unsigned long end)
> {
> struct mm_struct *mm = vma->vm_mm;
> - int nr_pages = (end - start) / PAGE_SIZE;
> + int error = 0;
> BUG_ON(!(vma->vm_flags & VM_LOCKED));
>
> /*
> @@ -289,8 +289,7 @@ int mlock_vma_pages_range(struct vm_area
> is_vm_hugetlb_page(vma) ||
> vma == get_gate_vma(current))) {
> downgrade_write(&mm->mmap_sem);
> - nr_pages = __mlock_vma_pages_range(vma, start, end, 1);
> -
> + error = __mlock_vma_pages_range(vma, start, end, 1);
> up_read(&mm->mmap_sem);
> /* vma can change or disappear */
> down_write(&mm->mmap_sem);
> @@ -298,22 +297,19 @@ int mlock_vma_pages_range(struct vm_area
> /* non-NULL vma must contain @start, but need to check @end */
> if (!vma || end > vma->vm_end)
> return -EAGAIN;
> - return nr_pages;
> + return error;
> }
>
> /*
> * User mapped kernel pages or huge pages:
> * make these pages present to populate the ptes, but
> - * fall thru' to reset VM_LOCKED--no need to unlock, and
> - * return nr_pages so these don't get counted against task's
> - * locked limit. huge pages are already counted against
> - * locked vm limit.
> + * fall thru' to reset VM_LOCKED--no need to unlock.
> */
> make_pages_present(start, end);
>
> no_mlock:
> vma->vm_flags &= ~VM_LOCKED; /* and don't come back! */
> - return nr_pages; /* pages NOT mlocked */
> + return error; /* pages NOT mlocked */
> }
>
>
> @@ -402,10 +398,6 @@ success:
> downgrade_write(&mm->mmap_sem);
>
> ret = __mlock_vma_pages_range(vma, start, end, 1);
> - if (ret > 0) {
> - mm->locked_vm -= ret;
> - ret = 0;
> - }
> /*
> * Need to reacquire mmap sem in write mode, as our callers
> * expect this. We have no support for atomically upgrading
> Index: b/mm/mmap.c
> ===================================================================
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -1229,10 +1229,10 @@ out:
> /*
> * makes pages present; downgrades, drops, reacquires mmap_sem
> */
> - int nr_pages = mlock_vma_pages_range(vma, addr, addr + len);
> - if (nr_pages < 0)
> - return nr_pages; /* vma gone! */
> - mm->locked_vm += (len >> PAGE_SHIFT) - nr_pages;
> + int error = mlock_vma_pages_range(vma, addr, addr + len);
> + if (error < 0)
> + return error; /* vma gone! */
> + mm->locked_vm += (len >> PAGE_SHIFT);
> } else if ((flags & MAP_POPULATE) && !(flags & MAP_NONBLOCK))
> make_pages_present(addr, addr + len);
> return addr;
> @@ -2087,7 +2087,7 @@ out:
> if (flags & VM_LOCKED) {
> int nr_pages = mlock_vma_pages_range(vma, addr, addr + len);
> if (nr_pages >= 0)
> - mm->locked_vm += (len >> PAGE_SHIFT) - nr_pages;
> + mm->locked_vm += (len >> PAGE_SHIFT);
> }
> return addr;
> undo_charge:
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-08-12 19:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 7:01 [RFC PATCH for -mm 0/5] mlock return value rework KOSAKI Motohiro
2008-08-11 7:04 ` [RFC PATCH for -mm 1/5] mlock() fix return values for mainline KOSAKI Motohiro
2008-08-12 20:39 ` Lee Schermerhorn
2008-08-13 8:03 ` KOSAKI Motohiro
2008-08-11 7:05 ` [RFC PATCH for -mm 2/5] related function comment fixes (optional) KOSAKI Motohiro
2008-08-12 19:02 ` Lee Schermerhorn
2008-08-13 8:37 ` KOSAKI Motohiro
2008-08-11 7:06 ` [RFC PATCH for -mm 3/5] kill unnecessary locked_vm adjustment KOSAKI Motohiro
2008-08-12 19:55 ` Lee Schermerhorn [this message]
2008-08-13 9:37 ` KOSAKI Motohiro
2008-08-15 13:54 ` Lee Schermerhorn
2008-08-18 9:23 ` KOSAKI Motohiro
2008-08-18 20:56 ` Lee Schermerhorn
2008-08-11 7:07 ` [RFC PATCH for -mm 4/5] fix mlock return value at munmap race KOSAKI Motohiro
2008-08-12 20:19 ` Lee Schermerhorn
2008-08-11 7:08 ` [RFC PATCH for -mm 5/5] fix mlock return value for mm KOSAKI Motohiro
2008-08-11 7:43 ` KOSAKI Motohiro
2008-08-12 20:30 ` Lee Schermerhorn
2008-08-13 8:36 ` KOSAKI Motohiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1218570910.6360.120.camel@lts-notebook \
--to=lee.schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox