From: Rajesh Ghanekar <rajeshsg@gmail.com>
To: Johannes Weiner <jweiner@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: what protects page lru list?
Date: Sun, 21 Aug 2011 00:15:28 +0530 [thread overview]
Message-ID: <CAOn_VZb5XqgvTweRY3unTLvrOE4DFMfJK5TDc3TeGk7ordPeUA@mail.gmail.com> (raw)
In-Reply-To: <20110820132701.GA29322@redhat.com>
Thanks Johannes. It makes sense. I was searching for any code in
which pages is on free list and being operated with lru_lock. But as
you said only pages on LRU lists are operated by lru_lock.
I am facing a panic in __rmqueue at list_del where the struct page
is corrupted or probably the free_list is corrupted. The kernel is
2.6.32.43.xxx from SLES11SP1. I will first see if any of the other code
(proprietary) running is not broken.
- Rajesh
On Sat, Aug 20, 2011 at 6:57 PM, Johannes Weiner <jweiner@redhat.com> wrote:
> On Sat, Aug 20, 2011 at 02:11:53AM +0530, Rajesh Ghanekar wrote:
>> Hi,
>> I am confused with what protects page->lru? Is it both zone->lru_lock or
>> zone->lock? I can see it being protected either by lru_lock or lock.
>
> It's not so much about page->lru but the actual list the page is
> linked to.
>
> The zone's lists of unallocated pages are protected by zone->lock,
> while the LRU lists with the pages for userspace are protected by
> zone->lru_lock.
>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-08-20 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 20:41 Rajesh Ghanekar
2011-08-20 13:27 ` Johannes Weiner
2011-08-20 18:45 ` Rajesh Ghanekar [this message]
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=CAOn_VZb5XqgvTweRY3unTLvrOE4DFMfJK5TDc3TeGk7ordPeUA@mail.gmail.com \
--to=rajeshsg@gmail.com \
--cc=jweiner@redhat.com \
--cc=linux-mm@kvack.org \
/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