All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [patch 2] mm: speculative get_page
Date: Tue, 28 Jun 2005 13:45:22 +0100	[thread overview]
Message-ID: <42C14662.40809@shadowen.org> (raw)
In-Reply-To: <42BF9D86.90204@yahoo.com.au>

Nick Piggin wrote:

>  #define PG_free			20	/* Page is on the free lists */
> +#define PG_freeing		21	/* PG_refcount about to be freed */

Wow this needs two new page bits.  That might be a problem ongoing.
There are only 24 of these puppies and this takes us to just two
remaining.  Do we really need _two_ to track free?

One obvious area of overlap might be the PG_nosave_free which seems to
be set on free pages for software suspend.  Perhaps that and PG_free
will be equivalent in intent (though maintained differently) and allow
us to recover a bit?

There are a couple of bits which imply ownership such as PG_slab,
PG_swapcache and PG_reserved which to my mind are all exclusive.
Perhaps those plus the PG_free could be combined into a owner field.  I
am unsure if the PG_freeing can be 'backed out' if not it may also combine?

Mumble ...

-apw

WARNING: multiple messages have this Message-ID (diff)
From: Andy Whitcroft <apw@shadowen.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [patch 2] mm: speculative get_page
Date: Tue, 28 Jun 2005 13:45:22 +0100	[thread overview]
Message-ID: <42C14662.40809@shadowen.org> (raw)
In-Reply-To: <42BF9D86.90204@yahoo.com.au>

Nick Piggin wrote:

>  #define PG_free			20	/* Page is on the free lists */
> +#define PG_freeing		21	/* PG_refcount about to be freed */

Wow this needs two new page bits.  That might be a problem ongoing.
There are only 24 of these puppies and this takes us to just two
remaining.  Do we really need _two_ to track free?

One obvious area of overlap might be the PG_nosave_free which seems to
be set on free pages for software suspend.  Perhaps that and PG_free
will be equivalent in intent (though maintained differently) and allow
us to recover a bit?

There are a couple of bits which imply ownership such as PG_slab,
PG_swapcache and PG_reserved which to my mind are all exclusive.
Perhaps those plus the PG_free could be combined into a owner field.  I
am unsure if the PG_freeing can be 'backed out' if not it may also combine?

Mumble ...

-apw
--
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:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2005-06-28 12:45 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27  6:29 [rfc] lockless pagecache Nick Piggin
2005-06-27  6:29 ` Nick Piggin
2005-06-27  6:32 ` [patch 1] mm: PG_free flag Nick Piggin
2005-06-27  6:32   ` [patch 2] mm: speculative get_page Nick Piggin
2005-06-27  6:33     ` [patch 3] radix tree: lookup_slot Nick Piggin
2005-06-27  6:34       ` [patch 4] radix tree: lockless readside Nick Piggin
2005-06-27  6:34         ` [patch 5] mm: lockless pagecache lookups Nick Piggin
2005-06-27  6:35           ` [patch 6] mm: spinlock tree_lock Nick Piggin
2005-06-27 14:12     ` [patch 2] mm: speculative get_page William Lee Irwin III
2005-06-27 14:12       ` William Lee Irwin III
2005-06-28  0:03       ` Nick Piggin
2005-06-28  0:03         ` Nick Piggin
2005-06-28  0:56         ` Nick Piggin
2005-06-28  0:56           ` Nick Piggin
2005-06-28  1:22         ` William Lee Irwin III
2005-06-28  1:22           ` William Lee Irwin III
2005-06-28  1:42           ` Nick Piggin
2005-06-28  1:42             ` Nick Piggin
2005-06-28  4:06             ` William Lee Irwin III
2005-06-28  4:06               ` William Lee Irwin III
2005-06-28  4:50               ` Nick Piggin
2005-06-28  4:50                 ` Nick Piggin
2005-06-28  5:08                 ` David S. Miller
2005-06-28  5:08                   ` [patch 2] mm: speculative get_page, " David S. Miller, Nick Piggin
2005-06-28  5:34                   ` Nick Piggin
2005-06-28  5:34                     ` Nick Piggin
2005-06-28 14:19                   ` William Lee Irwin III
2005-06-28 14:19                     ` William Lee Irwin III
2005-06-28 15:43                     ` Nick Piggin
2005-06-28 15:43                       ` Nick Piggin
2005-06-28 17:01                       ` Christoph Lameter
2005-06-28 17:01                         ` Christoph Lameter
2005-06-28 23:10                         ` Nick Piggin
2005-06-28 23:10                           ` Nick Piggin
2005-06-28 21:32                   ` Jesse Barnes
2005-06-28 21:32                     ` Jesse Barnes
2005-06-28 22:17                     ` Christoph Lameter
2005-06-28 22:17                       ` Christoph Lameter
2005-06-28 12:45     ` Andy Whitcroft [this message]
2005-06-28 12:45       ` Andy Whitcroft
2005-06-28 13:16       ` Nick Piggin
2005-06-28 13:16         ` Nick Piggin
2005-06-28 16:02         ` Dave Hansen
2005-06-28 16:02           ` Dave Hansen
2005-06-29 16:31           ` Pavel Machek
2005-06-29 16:31             ` Pavel Machek
2005-06-29 18:43             ` Dave Hansen
2005-06-29 18:43               ` Dave Hansen
2005-06-29 21:22               ` Pavel Machek
2005-06-29 21:22                 ` Pavel Machek
2005-06-29 16:31         ` Pavel Machek
2005-06-29 16:31           ` Pavel Machek
2005-06-27  6:43 ` VFS scalability (was: [rfc] lockless pagecache) Nick Piggin
2005-06-27  6:43   ` Nick Piggin
2005-06-27  7:13   ` Andi Kleen
2005-06-27  7:13     ` Andi Kleen
2005-06-27  7:33     ` VFS scalability Nick Piggin
2005-06-27  7:33       ` Nick Piggin
2005-06-27  7:44       ` Andi Kleen
2005-06-27  7:44         ` Andi Kleen
2005-06-27  8:03         ` Nick Piggin
2005-06-27  8:03           ` Nick Piggin
2005-06-27  7:46 ` [rfc] lockless pagecache Andrew Morton
2005-06-27  7:46   ` Andrew Morton
2005-06-27  8:02   ` Nick Piggin
2005-06-27  8:02     ` Nick Piggin
2005-06-27  8:15     ` Andrew Morton
2005-06-27  8:15       ` Andrew Morton
2005-06-27  8:28       ` Nick Piggin
2005-06-27  8:28         ` Nick Piggin
2005-06-27  8:56     ` Lincoln Dale
2005-06-27  8:56       ` Lincoln Dale
2005-06-27  9:04       ` Nick Piggin
2005-06-27  9:04         ` Nick Piggin
2005-06-27 18:14         ` Chen, Kenneth W
2005-06-27 18:14           ` Chen, Kenneth W
2005-06-27 18:50           ` Badari Pulavarty
2005-06-27 18:50             ` Badari Pulavarty
2005-06-27 19:05             ` Chen, Kenneth W
2005-06-27 19:05               ` Chen, Kenneth W
2005-06-27 19:22               ` Christoph Lameter
2005-06-27 19:22                 ` Christoph Lameter
2005-06-27 19:42                 ` Chen, Kenneth W
2005-06-27 19:42                   ` Chen, Kenneth W
2005-07-05 15:11                   ` Sonny Rao
2005-07-05 15:11                     ` Sonny Rao
2005-07-05 15:31                     ` Martin J. Bligh
2005-07-05 15:31                       ` Martin J. Bligh
2005-07-05 15:37                       ` Sonny Rao
2005-07-05 15:37                         ` Sonny Rao
2005-06-27 13:17     ` Benjamin LaHaise
2005-06-27 13:17       ` Benjamin LaHaise
2005-06-28  0:32       ` Nick Piggin
2005-06-28  0:32         ` Nick Piggin
2005-06-28  1:26         ` William Lee Irwin III
2005-06-28  1:26           ` William Lee Irwin III
2005-06-27 14:08   ` Martin J. Bligh
2005-06-27 14:08     ` Martin J. Bligh
2005-06-27 17:49   ` Christoph Lameter
2005-06-27 17:49     ` Christoph Lameter
2005-06-29 10:49 ` Hirokazu Takahashi
2005-06-29 10:49   ` Hirokazu Takahashi
2005-06-29 11:38   ` Nick Piggin
2005-06-29 11:38     ` Nick Piggin
2005-06-30  3:32     ` Hirokazu Takahashi
2005-06-30  3:32       ` Hirokazu Takahashi

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=42C14662.40809@shadowen.org \
    --to=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.