public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Aucoin@houston.rr.com
Cc: Christoph Lameter <clameter@sgi.com>,
	Andrew Morton <akpm@osdl.org>,
	"Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
	"'Kyle Moffett'" <mrmacman_g4@mac.com>,
	"'Tim Schmielau'" <tim@physik3.uni-rostock.de>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org, dcn@sgi.com
Subject: Re: la la la la ... swappiness
Date: Mon, 04 Dec 2006 12:38:19 -0600	[thread overview]
Message-ID: <45746B1B.5060809@mnsu.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0612041012010.32156@schroedinger.engr.sgi.com>

Hello,

Please forgive me if this is naive.  It seems that you could recompile 
your tar and patch commands to use the POSIX_FADVISE(2) feature with the 
POSIX_FADV_NOREUSE flags.  It seems these would cause the tar and patch 
commands to not clutter the page cache at all.

It'd be nice to be able to make a wrapper out of this kind of like the 
fakeroot(1) command like such as:

nocachesuck tar xvfz kernel.tar.gz

ya know what I mean?

-- 
Jeffrey Hundstad

  reply	other threads:[~2006-12-04 18:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04  1:54 la la la la ... swappiness Aucoin
2006-12-04  4:59 ` Andrew Morton
2006-12-04  7:22 ` Kyle Moffett
2006-12-04 14:39   ` Aucoin
2006-12-04 16:10     ` Chris Friesen
2006-12-04 17:07     ` Horst H. von Brand
2006-12-04 17:49       ` Aucoin
2006-12-04 18:44         ` Tim Schmielau
2006-12-04 21:28           ` Aucoin
2006-12-04 18:46         ` Horst H. von Brand
2006-12-04 21:43           ` Aucoin
2006-12-04 18:06       ` Andrew Morton
2006-12-04 18:15         ` Christoph Lameter
2006-12-04 18:38           ` Jeffrey Hundstad [this message]
2006-12-04 21:25             ` Aucoin
2006-12-04 21:43               ` Andrew Morton
2006-12-04 15:55   ` David Lang
2006-12-04 17:42     ` Aucoin
  -- strict thread matches above, loose matches on Subject: below --
2006-12-04 19:02 Al Boldi
     [not found] <200612030616.kB36GYBs019873@ms-smtp-03.texas.rr.com>
2006-12-03  8:08 ` Andrew Morton
2006-12-03 15:40   ` Aucoin
2006-12-03 20:46     ` Tim Schmielau
2006-12-03 23:56       ` Aucoin
2006-12-04  0:57         ` Horst H. von Brand
2006-12-04  4:56         ` Andrew Morton
2006-12-04  5:13           ` Linus Torvalds
2006-12-04 17:03             ` Christoph Lameter
2006-12-04 10:43         ` Nick Piggin
2006-12-04 14:45           ` Aucoin
2006-12-04 15:04             ` Nick Piggin
2006-12-05  4:02               ` Aucoin
2006-12-05  4:46                 ` Linus Torvalds
2006-12-05  6:41                   ` Aucoin
2006-12-05  7:01                     ` Nick Piggin
2006-12-05  7:26                       ` Rene Herman
2006-12-05 13:27                         ` Aucoin
2006-12-05 13:49                           ` Rene Herman
2006-12-05 13:25                       ` Aucoin
2006-12-03  6:18 Aucoin

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=45746B1B.5060809@mnsu.edu \
    --to=jeffrey.hundstad@mnsu.edu \
    --cc=Aucoin@houston.rr.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=dcn@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=tim@physik3.uni-rostock.de \
    --cc=torvalds@osdl.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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