Subject: Re: Odd swapping issue
From: Peter Zijlstra <peterz@infradead.org>
To: "Rafal Wijata (NULL)" <devnull@wijata.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <48888770.70702@wijata.com>
References: <488761F0.4040906@wijata.com>  <48888770.70702@wijata.com>
Content-Type: text/plain
Date: Thu, 24 Jul 2008 15:58:51 +0200
Message-Id: <1216907931.7257.333.camel@twins>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1419
Lines: 32

On Thu, 2008-07-24 at 15:45 +0200, Rafal Wijata (NULL) wrote:
> OK, things are little more clear now I suppose.
> 
> I tried (just for fun) echo 8 > /proc/sys/vm/nr_hugepages
> and it happened again, and no hugepages were allocated of course.
> 
> But this brought the following to my mind.
> 
> Since it's nfs server/client, and the nfs is rather heavily utilized(at 
> least sometimes), maybe nfsd tasks were unable to find long enough lowmem 
> chunk. How can we get such ram? By sweeping pages out to swap, isn't it?
> 
> Now the question is, if Linux actually has such feature like blind swapping 
> out if lowmem is too fragmented to find requested size?
> Can anybody confirm or negate?

Well, not blind - we have lumpy reclaim that tries to focus on the right
spot for large order allocations. However there are a myrad of
conditions that can make it impossible to reclaim certain pages,
therefore defeating this strategy.

> Next, I was thinking then I could run 64bit system, but I don't want to 
> reinstall it. Anybody knows if it's possible to have installed 32bit OS, but 
> run 64bit kernel alone(no 64bit glibc or anything else)?

Yes running as I type ;-)

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