From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, linux-mm@kvack.org
Subject: Re: why my systems never cache more than ~900 MB?
Date: Tue, 24 Mar 2009 17:00:53 +0100 [thread overview]
Message-ID: <49C903B5.8020504@wpkg.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0903241142510.13587@qirst.com>
Christoph Lameter schrieb:
> On Tue, 24 Mar 2009, Tomasz Chmielewski wrote:
>
>> Nick Piggin schrieb:
>> Does not help me, as what interests me here on these machines is mainly
>> caching block device data; they are iSCSI targets and access block devices
>> directly.
>
> You can run a 64 bit kernel on those machines. 64 bit kernels can use
> 32 bit userspace without a problem. Just install an additional kernel and
> try booting your existing setup with it.
>
>> What split should I choose to enable blockdev mapping on the whole memory on
>> 32 bit system with 3 or 4 GB RAM? Is it possible with 4 GB RAM at all?
>
> A 64 bit kernel will do the trick.
This hardware has problems booting 64 bit kernels (read: CPUs come from
the 32-bit land).
--
Tomasz Chmielewski
http://wpkg.org
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-24 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 8:42 why my systems never cache more than ~900 MB? Tomasz Chmielewski
2009-03-24 15:20 ` Nick Piggin
2009-03-24 15:35 ` Tomasz Chmielewski
2009-03-24 15:42 ` Nick Piggin
2009-03-24 15:44 ` Christoph Lameter
2009-03-24 16:00 ` Tomasz Chmielewski [this message]
2009-03-24 16:24 ` Christoph Lameter
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=49C903B5.8020504@wpkg.org \
--to=mangoo@wpkg.org \
--cc=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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;
as well as URLs for NNTP newsgroup(s).