All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>, Con Kolivas <kernel@kolivas.org>,
	Linux Memory Management <linux-mm@kvack.org>,
	Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: merging swap prefetching
Date: Sat, 10 Jun 2006 17:50:33 +1000	[thread overview]
Message-ID: <448A79C9.5000500@yahoo.com.au> (raw)

I wasn't aware there was a push to merge swap prefetching in
2.6.18, until the -mm merge plans post.

I would have expected to see some numbers, however I guess the
"merge unless proven bad" approach for new features works too.

I had a quick look at the code, and I think it still needs
more cleanup and review... it is vaguely difficult to participate
in discussions about these patches because they are often split
over several iterations of versions/fixes, and because it isn't
always clear what they depend on (although in the case of swap
prefetching, that isn't so much of a problem).

And also, there is no linux-mm thread to reply to... could we
have some of the intrusive mm/ patches intended for 2.6.18
posted here before they get merged, or is that too much trouble?

As far as swap prefetching itself goes, I still don't like it
much (same issues still stand), but with some cleaning up the
patch shouldn't be too bad, and I can turn it off... so if people
want it and if numbers show it is working, I wouldn't object.

-- 
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: Andrew Morton <akpm@osdl.org>, Con Kolivas <kernel@kolivas.org>,
	Linux Memory Management <linux-mm@kvack.org>,
	Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>
Subject: merging swap prefetching
Date: Sat, 10 Jun 2006 17:50:33 +1000	[thread overview]
Message-ID: <448A79C9.5000500@yahoo.com.au> (raw)

I wasn't aware there was a push to merge swap prefetching in
2.6.18, until the -mm merge plans post.

I would have expected to see some numbers, however I guess the
"merge unless proven bad" approach for new features works too.

I had a quick look at the code, and I think it still needs
more cleanup and review... it is vaguely difficult to participate
in discussions about these patches because they are often split
over several iterations of versions/fixes, and because it isn't
always clear what they depend on (although in the case of swap
prefetching, that isn't so much of a problem).

And also, there is no linux-mm thread to reply to... could we
have some of the intrusive mm/ patches intended for 2.6.18
posted here before they get merged, or is that too much trouble?

As far as swap prefetching itself goes, I still don't like it
much (same issues still stand), but with some cleaning up the
patch shouldn't be too bad, and I can turn it off... so if people
want it and if numbers show it is working, I wouldn't object.

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

             reply	other threads:[~2006-06-10  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10  7:50 Nick Piggin [this message]
2006-06-10  7:50 ` merging swap prefetching Nick Piggin
2006-06-10  8:11 ` Andrew Morton
2006-06-10  8:11   ` Andrew Morton

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=448A79C9.5000500@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.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.