linux-kernel - RE: la la la la ... swappiness

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200612041749.kB4HnDNw008901@ms-smtp-02.texas.rr.com>
Date:	Mon, 4 Dec 2006 11:49:12 -0600
From:	"Aucoin" <Aucoin@...ston.RR.com>
To:	"'Horst H. von Brand'" <vonbrand@....utfsm.cl>
Cc:	"'Kyle Moffett'" <mrmacman_g4@....com>,
	"'Tim Schmielau'" <tim@...sik3.uni-rostock.de>,
	"'Andrew Morton'" <akpm@...l.org>, <torvalds@...l.org>,
	<linux-kernel@...r.kernel.org>, <clameter@....com>
Subject: RE: la la la la ... swappiness



> From: Horst H. von Brand [mailto:vonbrand@....utfsm.cl]
> That means that there isn't a need for that memory at all (and so they

In the current isolated non-production, not actually bearing a load test
case yes. But if I can't get it to not swap on an idle system I have no hope
of avoiding OOM on a loaded system.

> In any case, how do you know it is the tar data that stays around, and not
> just that the number of pages "in use" stays roughly constant?

I'm not dumping the contents of memory so I don't.

> - What you are doing, step by step

Trying to deliver a high availability, linearly scalable, clustered iSCSI
storage solution that can be upgraded with minimum downtime.

> - What are your exact requirements

OOM not to kill anything.

> - In what exact way is it missbehaving. Please tell /in detail/ how you

OOM kills important stuff.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/