All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stone Wang" <pwstone@gmail.com>
To: "Andi Kleen" <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic
Date: Fri, 24 Mar 2006 09:54:17 -0500	[thread overview]
Message-ID: <bc56f2f0603240654n4b978cb0p@mail.gmail.com> (raw)
In-Reply-To: <p73bqvv6ha9.fsf@verdi.suse.de>

I am preparing patch for 2.6.16, replace the name "wired" with "pinned".

Potentially, the list could be used for more purposes, than just mlocked pages.

Shaoping Wang

24 Mar 2006 15:36:46 +0100, Andi Kleen <ak@suse.de>:
> "Stone Wang" <pwstone@gmail.com> writes:
> >    mlocked areas.
> > 2. More consistent LRU semantics in Memory Management.
> >    Mlocked pages is placed on a separate LRU list: Wired List.
>
> If it's mlocked why don't you just called it Mlocked list?
> Strange jargon makes the patch cooler? Also in meminfo
>
> -Andi
>

WARNING: multiple messages have this Message-ID (diff)
From: "Stone Wang" <pwstone@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic
Date: Fri, 24 Mar 2006 09:54:17 -0500	[thread overview]
Message-ID: <bc56f2f0603240654n4b978cb0p@mail.gmail.com> (raw)
In-Reply-To: <p73bqvv6ha9.fsf@verdi.suse.de>

I am preparing patch for 2.6.16, replace the name "wired" with "pinned".

Potentially, the list could be used for more purposes, than just mlocked pages.

Shaoping Wang

24 Mar 2006 15:36:46 +0100, Andi Kleen <ak@suse.de>:
> "Stone Wang" <pwstone@gmail.com> writes:
> >    mlocked areas.
> > 2. More consistent LRU semantics in Memory Management.
> >    Mlocked pages is placed on a separate LRU list: Wired List.
>
> If it's mlocked why don't you just called it Mlocked list?
> Strange jargon makes the patch cooler? Also in meminfo
>
> -Andi
>

--
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>

  reply	other threads:[~2006-03-24 14:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 13:35 [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic Stone Wang
2006-03-20 13:41 ` Arjan van de Ven
2006-03-20 13:41   ` Arjan van de Ven
2006-03-20 23:52   ` Nate Diller
2006-03-20 23:52     ` Nate Diller
2006-03-21  7:10     ` Arjan van de Ven
2006-03-21  7:10       ` Arjan van de Ven
2006-03-21 12:24     ` Nick Piggin
2006-03-21 12:24       ` Nick Piggin
2006-03-20 17:27 ` Christoph Lameter
2006-03-20 17:27   ` Christoph Lameter
2006-03-21  5:23   ` Stone Wang
2006-03-21  5:23     ` Stone Wang
2006-03-21 15:20   ` Stone Wang
2006-03-21 15:20     ` Stone Wang
2006-03-24  4:45   ` Rik van Riel
2006-03-24  4:45     ` Rik van Riel
2006-03-21 12:20 ` Nick Piggin
2006-03-21 12:20   ` Nick Piggin
2006-03-24 15:05   ` Stone Wang
2006-03-24 15:05     ` Stone Wang
2006-03-24 16:57     ` Nick Piggin
2006-03-24 16:57       ` Nick Piggin
2006-03-24 14:36 ` Andi Kleen
2006-03-24 14:36   ` Andi Kleen
2006-03-24 14:54   ` Stone Wang [this message]
2006-03-24 14:54     ` Stone Wang

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=bc56f2f0603240654n4b978cb0p@mail.gmail.com \
    --to=pwstone@gmail.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.