[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c0942db0608190953r71ad8716vc2d11d9366894e40@mail.gmail.com>
Date: Sat, 19 Aug 2006 09:53:54 -0700
From: "Ray Lee" <madrabbit@...il.com>
To: "Andrew Morton" <akpm@...l.org>
Cc: "Daniel Phillips" <phillips@...gle.com>,
"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"David Miller" <davem@...emloft.net>, riel@...hat.com,
tgraf@...g.ch, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, "Mike Christie" <michaelc@...wisc.edu>
Subject: Re: [RFC][PATCH 2/9] deadlock prevention core
On 8/18/06, Andrew Morton <akpm@...l.org> wrote:
> I assert that this can be solved by putting swap on local disks. Peter
> asserts that this isn't acceptable due to disk unreliability. I point
> out that local disk reliability can be increased via MD, all goes quiet.
>
> A good exposition which helps us to understand whether and why a
> significant proportion of the target user base still wishes to do
> swap-over-network would be useful.
Adding a hard drive adds $low per system, another failure point, and
more importantly ~3-10 Watts which then has to be paid for twice (once
to power it, again to cool it). For a hundred seats, that's
significant. For 500, it's ranging toward fully painful.
I'm in the process of designing the next upgrade for a VoIP call
center, and we want to go entirely diskless in the agent systems. We'd
also rather not swap over the network, but 'swap is as swap does.'
That said, it in no way invalidates using /proc/sys/vm/min_free_kbytes...
Ray
-
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/
Powered by blists - more mailing lists