From: Peter Zijlstra <peterz@infradead.org>
To: "Rafal Wijata (NULL)" <devnull@wijata.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Odd swapping issue
Date: Thu, 24 Jul 2008 15:58:51 +0200 [thread overview]
Message-ID: <1216907931.7257.333.camel@twins> (raw)
In-Reply-To: <48888770.70702@wijata.com>
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 ;-)
prev parent reply other threads:[~2008-07-24 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:53 Odd swapping issue Rafal Wijata
2008-07-23 17:50 ` Peter Zijlstra
2008-07-23 21:17 ` David Newall
2008-07-24 2:20 ` Dan Noé
2008-07-24 6:39 ` Peter Zijlstra
2008-07-24 11:51 ` KOSAKI Motohiro
2008-07-24 13:45 ` Rafal Wijata (NULL)
2008-07-24 13:58 ` Peter Zijlstra [this message]
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=1216907931.7257.333.camel@twins \
--to=peterz@infradead.org \
--cc=devnull@wijata.com \
--cc=linux-kernel@vger.kernel.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