From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: jim@rubylane.com, Andrew Morton <akpm@zip.com.au>
Cc: linux-mm@kvack.org
Subject: Re: 2.2.20 suspends everything then recovers during heavy I/O
Date: Fri, 05 Apr 2002 10:47:28 -0800 [thread overview]
Message-ID: <1648866003.1018003647@[10.10.2.3]> (raw)
In-Reply-To: <20020405182738.19092.qmail@london.rubylane.com>
> What would be really great is some way to indicate, maybe with an
> O_SEQ flag or something, that an application is going to sequentially
> access a file, so cacheing it is a no-win proposition. Production
> servers do have situations where lots of data has to be copied or
> accessed, for example, to do a backup, but doing a backup shouldn't
> mean that all of the important stuff gets continuously thrown out of
> memory while the backup is running. Saving metadata during a backup
> is useful. Saving file data isn't. It's seems hard to do this
> without an application hint because I may scan a database
> sequentially but I'd still want those buffers to stay resident.
Doesn't the raw IO stuff do this, effectively?
M.
--
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/
next prev parent reply other threads:[~2002-04-05 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 22:06 Jim Wilcoxson
2002-04-05 5:29 ` Andrew Morton
2002-04-05 18:27 ` jim
2002-04-05 18:47 ` Martin J. Bligh [this message]
2002-04-05 19:52 ` jim
2002-04-05 19:55 ` jim
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='1648866003.1018003647@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=jim@rubylane.com \
--cc=linux-mm@kvack.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