From: MinChan Kim <minchan.kim@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux mm <linux-mm@kvack.org>,
linux kernel <linux-kernel@vger.kernel.org>,
Nick Piggin <npiggin@suse.de>, Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH v2] fix mlocked page counter mistmatch
Date: Thu, 5 Feb 2009 08:35:43 +0900 [thread overview]
Message-ID: <20090204233543.GA26159@barrios-desktop> (raw)
In-Reply-To: <20090204171639.ECCE.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Wed, Feb 04, 2009 at 07:28:19PM +0900, KOSAKI Motohiro wrote:
> > With '29-rc3-git5', I found,
> >
> > static int try_to_mlock_page(struct page *page, struct vm_area_struct *vma)
> > {
> > int mlocked = 0;
> >
> > if (down_read_trylock(&vma->vm_mm->mmap_sem)) {
> > if (vma->vm_flags & VM_LOCKED) {
> > mlock_vma_page(page);
> > mlocked++; /* really mlocked the page */
> > }
> > up_read(&vma->vm_mm->mmap_sem);
> > }
> > return mlocked;
> > }
> >
> > It still try to downgrade mmap_sem.
> > Do I miss something ?
>
> sorry, I misunderstood your "downgrade". I said linus removed downgrade_write(&mma_sem).
>
> Now, I understand this issue perfectly. I agree you and lee-san's fix is correct.
> Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Good. I will send adrew with your ACK agian.
>
>
> and, I think current try_to_mlock_page() is correct. no need change.
> Why?
>
> 1. Generally, mmap_sem holding is necessary when vma->vm_flags accessed.
> that's vma's basic rule.
> 2. However, try_to_unmap_one() doesn't held mamp_sem. but that's ok.
> it often get incorrect result. but caller consider incorrect value safe.
> 3. try_to_mlock_page() need mmap_sem because it obey rule (1).
> 4. in try_to_mlock_page(), if down_read_trylock() is failure,
> we can't move the page to unevictable list. but that's ok.
> the page in evictable list is periodically try to reclaim. and
> be called try_to_unmap().
> try_to_unmap() (and its caller) also move the unevictable page to unevictable list.
> Therefore, in long term view, the page leak is not happend.
Thanks for clarification.
In long term view, you're right.
but My concern is that munlock[all] pathes always hold down of mmap_sem.
After all, down_read_trylock always wil fail for such cases.
So, current task's mlocked pages only can be reclaimed
by background or direct reclaim path if the task don't exit.
I think it can increase reclaim overhead unnecessary
if there are lots of such tasks.
What's your opinion ?
>
> this explanation is enough?
>
> thanks.
>
--
Kinds Regards
MinChan Kim
--
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:[~2009-02-04 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 4:24 MinChan Kim
2009-02-03 16:44 ` KOSAKI Motohiro
2009-02-03 23:44 ` MinChan Kim
2009-02-04 2:12 ` KOSAKI Motohiro
2009-02-04 2:44 ` MinChan Kim
2009-02-04 2:51 ` KOSAKI Motohiro
2009-02-04 4:57 ` MinChan Kim
2009-02-04 10:28 ` KOSAKI Motohiro
2009-02-04 14:07 ` Lee Schermerhorn
2009-02-04 23:38 ` MinChan Kim
2009-02-04 23:35 ` MinChan Kim [this message]
2009-02-05 2:17 ` KOSAKI Motohiro
2009-02-05 2:32 ` MinChan Kim
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=20090204233543.GA26159@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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