From: "Gregory Giguashvili" <Gregoryg@ParadigmGeo.com>
To: linux-mm@kvack.org
Subject: RE: Correctly determine free memory amount before swapping
Date: Mon, 13 Dec 2004 08:32:24 +0200 [thread overview]
Message-ID: <06EF4EE36118C94BB3331391E2CDAAD9D4A41F@exil1.paradigmgeo.net> (raw)
> I need to commit the largest chunk of memory in the quickest way. This
operation may
> be slowed down by swapping - that's why I don't want to get there.
Could any of MM people throw a short comment on this? If a rough
estimation is impossible to give in Linux, it would be great to know
that.
Thanks in advance,
Giga
P.S. If I'm not asking this question in the right mailing list, please,
let me know.
--
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:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2004-12-13 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 6:32 Gregory Giguashvili [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 14:17 Gregory Giguashvili
2004-12-13 9:34 ` Robin Holt
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=06EF4EE36118C94BB3331391E2CDAAD9D4A41F@exil1.paradigmgeo.net \
--to=gregoryg@paradigmgeo.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