From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org
Cc: gfiala@s.netic.de
Subject: Re: large files unnecessary trashing filesystem cache?
Date: Wed, 19 Oct 2005 17:54:11 +0200 [thread overview]
Message-ID: <200510191754.17963.ioe-lkml@rameria.de> (raw)
In-Reply-To: <1129720232.435629a8753d3@webmail.LF.net>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
Hi,
On Wednesday 19 October 2005 13:10, gfiala@s.netic.de wrote:
> Zitat von Andrew Morton <akpm@osdl.org>:
> > So I'd also suggest a new resource limit which, if set, is copied into the
> > applications's file_structs on open(). So you then write a little wrapper
> > app which does setrlimit()+exec():
> >
> > limit-cache-usage -s 1000 my-fave-backup-program <args>
> >
> > Which will cause every file which my-fave-backup-program reads or writes to
> > be limited to a maximum pagecache residency of 1000 kbytes.
>
> Or make it another 'ulimit' parameter...
Which is already there: There is an ulimit for "maximum RSS",
which is at least a superset of "maximum pagecache residency".
This is already settable and known by many admins. But AFAIR it is not
honoured by the kernel completely, right?
But per file is a much better choice, since this would allow
concurrent streaming. This is needed to implement timeshifting at least[1].
So either I miss something or this is no proper solution yet.
Regards
Ingo Oeser
[1] Which is obviously done by some kind of on-disk FIFO.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-19 15:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 20:01 Guido Fiala
2005-10-18 20:48 ` Badari Pulavarty
2005-10-20 15:23 ` Guido Fiala
2005-10-19 3:02 ` Andrew James Wade
2005-10-19 4:37 ` Andrew Morton
2005-10-19 5:45 ` Andrew James Wade
2005-10-19 11:01 ` gfiala
2005-10-19 11:10 ` gfiala
2005-10-19 15:54 ` Ingo Oeser [this message]
2005-10-19 19:49 ` Andrew Morton
2005-10-19 22:26 ` Paul Jackson
2005-10-20 6:28 ` Ingo Oeser
2005-10-19 4:10 ` Lee Revell
2005-10-19 15:43 ` Badari Pulavarty
2005-10-19 17:58 ` Guido Fiala
2005-10-19 18:43 ` Kyle Moffett
2005-10-19 18:52 ` Guido Fiala
[not found] <4Z5WG-1iM-19@gated-at.bofh.it>
[not found] ` <4Z6zs-27l-39@gated-at.bofh.it>
2005-10-18 21:58 ` Bodo Eggert
2005-10-18 23:05 ` Badari Pulavarty
2005-10-19 0:20 ` David Lang
2005-10-19 0:33 ` Fawad Lateef
2005-10-19 1:42 ` Bernd Eckenfels
2005-10-19 7:23 ` Bodo Eggert
2005-10-19 11:06 ` gfiala
2005-10-19 13:43 ` Avi Kivity
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=200510191754.17963.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=gfiala@s.netic.de \
--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
all inboxes | Powered by JetHome®