From: Bill Davidsen <davidsen@tmr.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, Andrea Arcangeli <andrea@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: VM patches (please review)
Date: Wed, 04 Feb 2004 12:16:00 -0500 [thread overview]
Message-ID: <402128D0.2020509@tmr.com> (raw)
In-Reply-To: <402065DE.9090902@cyberone.com.au>
Nick Piggin wrote:
> http://www.kerneltrap.org/~npiggin/vm/
> (may need to reload)
>
> Here are the patches to go with my earlier post.
> kernel is 2.6.2-rc3-mm1.
>
> I'm suire I've upset at least one uncommented^Wdivine
> balance so if anyone has time to review and comment
> it would be appreciated.
>
> I can email the patches to the lists if anyone would
> like?
Since this is broken down nicely, a line or two about what each patch
does or doesn't address would be useful. In particular, having just
gotten a working RSS I'm suspicious of the patch named vm-no-rss-limit
being desirable ;-)
Nice work, but it would be nice to see what problem a patch addresses to
check for blowback under some other load.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
WARNING: multiple messages have this Message-ID (diff)
From: Bill Davidsen <davidsen@tmr.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, Andrea Arcangeli <andrea@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: VM patches (please review)
Date: Wed, 04 Feb 2004 12:16:00 -0500 [thread overview]
Message-ID: <402128D0.2020509@tmr.com> (raw)
In-Reply-To: <402065DE.9090902@cyberone.com.au>
Nick Piggin wrote:
> http://www.kerneltrap.org/~npiggin/vm/
> (may need to reload)
>
> Here are the patches to go with my earlier post.
> kernel is 2.6.2-rc3-mm1.
>
> I'm suire I've upset at least one uncommented^Wdivine
> balance so if anyone has time to review and comment
> it would be appreciated.
>
> I can email the patches to the lists if anyone would
> like?
Since this is broken down nicely, a line or two about what each patch
does or doesn't address would be useful. In particular, having just
gotten a working RSS I'm suspicious of the patch named vm-no-rss-limit
being desirable ;-)
Nice work, but it would be nice to see what problem a patch addresses to
check for blowback under some other load.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
--
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>
next prev parent reply other threads:[~2004-02-04 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 3:24 VM patches (please review) Nick Piggin
2004-02-04 3:24 ` Nick Piggin
2004-02-04 17:16 ` Bill Davidsen [this message]
2004-02-04 17:16 ` Bill Davidsen
2004-02-04 17:40 ` Rik van Riel
2004-02-04 17:40 ` Rik van Riel
2004-02-04 23:55 ` Bill Davidsen
2004-02-04 23:55 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 23:00 marcel cotta
2004-02-06 23:05 ` Nick Piggin
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=402128D0.2020509@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.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.