public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chase Venters <chase.venters@clientec.com>
To: ck@vds.kolivas.org
Cc: Con Kolivas <kernel@kolivas.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [ck] swap prefetching merge plans
Date: Tue, 28 Mar 2006 00:16:15 -0600	[thread overview]
Message-ID: <200603280016.38327.chase.venters@clientec.com> (raw)
In-Reply-To: <200603231804.36334.kernel@kolivas.org>

On Thursday 23 March 2006 01:04, Con Kolivas wrote:
> For those users who feel they do have a compelling argument for it, please
> speak now or I'll end up maintaining this in -ck only forever.  I've come
> to depend on it with my workloads now so I'm never dropping it. There's no
> point me explaining how it is useful yet again, though, because I just end
> up looking like I'm handwaving. It seems a shame for it not to be available
> to all linux users.

Another happy prefetch user chiming in (sadly, without rigorous scientific 
research -- my team of monkeys is too busy at the moment). In my case, I have 
a gig of RAM, but I'm a pig when it comes to leaving applications open. 

Testimonials may not meet the appropriate criteria for merging a patch; I 
hope, though, that the aggregate value of these messages, in considering this 
issue, is more than that of mere noise.

> Cheers,
> Con

Thanks,
Chase

  parent reply	other threads:[~2006-03-28  6:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  4:53 -mm merge plans Andrew Morton
2006-03-23  7:04 ` swap prefetching " Con Kolivas
2006-03-23  7:56   ` [ck] " Grzegorz Kulewski
2006-03-23  8:01   ` jos poortvliet
2006-03-23  8:22     ` Nick Piggin
2006-03-23  9:09       ` Con Kolivas
2006-03-23  9:24         ` Con Kolivas
2006-03-23 13:23       ` Martin J. Bligh
2006-03-23  8:33     ` Thomas Kuther
2006-03-23 11:19   ` Jesper Juhl
2006-03-23 11:24   ` [ck] " André Goddard Rosa
2006-03-23 11:57   ` Spike
2006-03-23 12:03     ` Spike
2006-03-23 12:16     ` Spike
2006-03-23 11:58   ` Lenar Lõhmus
2006-03-23 13:58   ` Francesco Biscani
2006-03-23 15:37     ` James Rayner
2006-03-23 15:34   ` [ck] " Radoslaw Szkodzinski
2006-03-23 18:35   ` Mattia Dongili
2006-03-23 18:40   ` Rafael J. Wysocki
2006-03-25 14:37   ` Jan Engelhardt
2006-03-25 15:24     ` Nick Piggin
2006-03-25 23:44       ` Con Kolivas
2006-03-26  5:54         ` Mike Galbraith
2006-03-26  8:08           ` Con Kolivas
2006-03-26  7:42             ` Mike Galbraith
2006-03-26  9:34               ` Con Kolivas
2006-03-27 15:37                 ` [ck] " André Goddard Rosa
2006-03-27 22:19                   ` Con Kolivas
2006-03-26  9:20         ` Jan Engelhardt
2006-03-28  6:16   ` Chase Venters [this message]
2006-03-23  7:59 ` -mm " Ryan M.
2006-03-23  8:09   ` [ck] " Jens Axboe
2006-03-23  9:07     ` Con Kolivas
2006-03-23 12:12       ` [ck] " Jens Axboe
2006-03-23 10:39 ` Takashi Iwai
2006-03-23 12:33 ` Christoph Hellwig
2006-03-23 12:49 ` [PATCH] remove pps support Roman Zippel
2006-03-23 13:43 ` -mm merge plans Michal Piotrowski
2006-03-24 23:33 ` Eric W. Biederman
2006-03-24 23:53   ` Andrew Morton
2006-03-25  0:50     ` Eric W. Biederman
2006-03-25  1:53 ` Arthur Othieno

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=200603280016.38327.chase.venters@clientec.com \
    --to=chase.venters@clientec.com \
    --cc=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox