From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, ck@vds.kolivas.org, pj@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Implement Swap Prefetching v23
Date: Fri, 10 Feb 2006 15:17:47 +1100 [thread overview]
Message-ID: <43EC13EB.3010501@yahoo.com.au> (raw)
In-Reply-To: <200602101514.40140.kernel@kolivas.org>
Con Kolivas wrote:
> On Friday 10 February 2006 15:07, Nick Piggin wrote:
>>Well they go on the head of the inactive list and will kick out file
>>backed pagecache. Which was my concern about reducing the usefulness
>>of useful swapping on desktop systems.
>
>
> Ok I see. We don't have a way to add to the tail of that list though? Is that
> a worthwhile addition to this (ever growing) project? That would definitely
Don't know, can you tell us?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, ck@vds.kolivas.org, pj@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Implement Swap Prefetching v23
Date: Fri, 10 Feb 2006 15:17:47 +1100 [thread overview]
Message-ID: <43EC13EB.3010501@yahoo.com.au> (raw)
In-Reply-To: <200602101514.40140.kernel@kolivas.org>
Con Kolivas wrote:
> On Friday 10 February 2006 15:07, Nick Piggin wrote:
>>Well they go on the head of the inactive list and will kick out file
>>backed pagecache. Which was my concern about reducing the usefulness
>>of useful swapping on desktop systems.
>
>
> Ok I see. We don't have a way to add to the tail of that list though? Is that
> a worthwhile addition to this (ever growing) project? That would definitely
Don't know, can you tell us?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2006-02-10 4:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 2:55 [PATCH] mm: Implement Swap Prefetching v23 Con Kolivas
2006-02-10 2:55 ` Con Kolivas
2006-02-10 3:25 ` Andrew Morton
2006-02-10 3:25 ` Andrew Morton
2006-02-10 3:49 ` Con Kolivas
2006-02-10 3:49 ` Con Kolivas
2006-02-10 4:07 ` Nick Piggin
2006-02-10 4:07 ` Nick Piggin
2006-02-10 4:14 ` Con Kolivas
2006-02-10 4:14 ` Con Kolivas
2006-02-10 4:17 ` Nick Piggin [this message]
2006-02-10 4:17 ` Nick Piggin
2006-02-10 4:25 ` Andrew Morton
2006-02-10 4:25 ` Andrew Morton
2006-02-10 4:45 ` Nick Piggin
2006-02-10 4:45 ` Nick Piggin
2006-02-10 4:55 ` Andrew Morton
2006-02-10 4:55 ` Andrew Morton
2006-02-10 5:01 ` Nick Piggin
2006-02-10 5:01 ` Nick Piggin
2006-02-10 5:26 ` Con Kolivas
2006-02-10 5:26 ` Con Kolivas
2006-02-10 5:32 ` Nick Piggin
2006-02-10 5:32 ` Nick Piggin
2006-02-10 5:37 ` Con Kolivas
2006-02-10 5:37 ` Con Kolivas
2006-02-10 5:43 ` Nick Piggin
2006-02-10 5:43 ` Nick Piggin
2006-02-10 5:48 ` Con Kolivas
2006-02-10 5:48 ` Con Kolivas
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=43EC13EB.3010501@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.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 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.