All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>
Cc: "Aubrey Li" <aubreylee@gmail.com>,
	"Vaidyanathan Srinivasan" <svaidy@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	"Linus Torvalds" <torvalds@osdl.org>,
	"Andrew Morton" <akpm@osdl.org>,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	"Robin Getz" <rgetz@blackfin.uclinux.org>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>
Subject: Re: [RPC][PATCH 2.6.20-rc5] limit total vfs page cache
Date: Fri, 19 Jan 2007 21:35:43 -0500	[thread overview]
Message-ID: <8bd0f97a0701191835y49a61e7jb65a3b63f906ca56@mail.gmail.com> (raw)
In-Reply-To: <45B17D6D.2030004@yahoo.com.au>

On 1/19/07, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Luckily, there are actually good, robust solutions for your higher
> order allocation problem. Do higher order allocations at boot time,
> modifiy userspace applications, or set up otherwise-unused, or easily
> reclaimable reserve pools for higher order allocations. I don't
> understand why you are so resistant to all of these approaches?

in a nutshell ...

the idea is to try and generalize these things

your approach involves tweaking each end solution to maximize the performance

our approach is to teach the kernel some more tricks so that each
solution need not be tweaked

these are at obvious odds as they tackle the problem by going in
pretty much opposite directions ... yours leads to a tighter system in
the end, but ours leads to much more rapid development and deployment
-mike

WARNING: multiple messages have this Message-ID (diff)
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Aubrey Li <aubreylee@gmail.com>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Robin Getz <rgetz@blackfin.uclinux.org>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>
Subject: Re: [RPC][PATCH 2.6.20-rc5] limit total vfs page cache
Date: Fri, 19 Jan 2007 21:35:43 -0500	[thread overview]
Message-ID: <8bd0f97a0701191835y49a61e7jb65a3b63f906ca56@mail.gmail.com> (raw)
In-Reply-To: <45B17D6D.2030004@yahoo.com.au>

On 1/19/07, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Luckily, there are actually good, robust solutions for your higher
> order allocation problem. Do higher order allocations at boot time,
> modifiy userspace applications, or set up otherwise-unused, or easily
> reclaimable reserve pools for higher order allocations. I don't
> understand why you are so resistant to all of these approaches?

in a nutshell ...

the idea is to try and generalize these things

your approach involves tweaking each end solution to maximize the performance

our approach is to teach the kernel some more tricks so that each
solution need not be tweaked

these are at obvious odds as they tackle the problem by going in
pretty much opposite directions ... yours leads to a tighter system in
the end, but ours leads to much more rapid development and deployment
-mike

--
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:[~2007-01-20  2:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18  3:23 [RPC][PATCH 2.6.20-rc5] limit total vfs page cache Aubrey Li
2007-01-18  3:23 ` Aubrey Li
2007-01-19 14:44 ` Vaidyanathan Srinivasan
2007-01-19 14:44   ` Vaidyanathan Srinivasan
2007-01-19 15:40   ` Aubrey Li
2007-01-19 15:40     ` Aubrey Li
2007-01-24  5:30     ` Vaidyanathan Srinivasan
2007-01-24  5:30       ` Vaidyanathan Srinivasan
2007-01-24  5:53       ` Aubrey Li
2007-01-24  5:53         ` Aubrey Li
2007-01-19 14:52 ` Vaidyanathan Srinivasan
2007-01-19 14:52   ` Vaidyanathan Srinivasan
2007-01-19 16:05   ` Aubrey Li
2007-01-19 16:05     ` Aubrey Li
2007-01-19 18:49     ` Vaidyanathan Srinivasan
2007-01-19 18:49       ` Vaidyanathan Srinivasan
2007-01-19 19:01       ` Christoph Lameter
2007-01-19 19:01         ` Christoph Lameter
2007-01-20  2:04       ` Aubrey Li
2007-01-20  2:04         ` Aubrey Li
2007-01-20  2:24         ` Nick Piggin
2007-01-20  2:24           ` Nick Piggin
2007-01-20  2:35           ` Mike Frysinger [this message]
2007-01-20  2:35             ` Mike Frysinger
2007-01-20  2:49             ` Nick Piggin
2007-01-20  2:49               ` Nick Piggin
2007-01-20  3:40               ` Mike Frysinger
2007-01-20  3:40                 ` Mike Frysinger
2007-01-20  3:08           ` Aubrey Li
2007-01-20  3:08             ` Aubrey Li
2007-01-20  4:03             ` Nick Piggin
2007-01-20  4:03               ` Nick Piggin
2007-01-20  4:26               ` Aubrey Li
2007-01-20  4:26                 ` Aubrey Li
2007-01-22 19:22                 ` Christoph Lameter
2007-01-22 19:22                   ` Christoph Lameter
2007-01-22 19:15               ` Christoph Lameter
2007-01-22 19:15                 ` Christoph Lameter
2007-01-19 18:21 ` Christoph Lameter
2007-01-19 18:21   ` Christoph Lameter

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=8bd0f97a0701191835y49a61e7jb65a3b63f906ca56@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=akpm@osdl.org \
    --cc=aubreylee@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-os@analogic.com \
    --cc=nickpiggin@yahoo.com.au \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=svaidy@linux.vnet.ibm.com \
    --cc=torvalds@osdl.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.