From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] What is for 64 bit 9front?
Date: Sun, 10 Aug 2014 10:44:44 -0400 [thread overview]
Message-ID: <44018b84589bc1bce1c713f6c7d2a350@ladd.quanstro.net> (raw)
In-Reply-To: <c028be6baa12d634f6cb86e41ee16ed0@felloff.net>
On Fri Aug 8 21:28:00 EDT 2014, cinap_lenrek@felloff.net wrote:
> for me, its the opposite. my fileserver and cpu servers
> are 32 bit machines, but i use thinkpad x230 which has
> 16gb of ram as a terminal. 64bit is just normal now on
> the pc and having huge (kernel) virtual address space
> solves problems like running out of space for devdraw
> bitmaps or having to tmpmap the page tables.
that is really a question of KZERO. if you're running out of
space for big things in kernel space on any 32-bit terminal, and
you don't have need for processes >=3g, then just move KZERO
down to 0xc0000000. i have verified KZERO down to 0x80000000
work. this shouldn't be a surprise since this was KZERO until
recently. make sure to change KTZERO in mkfile.
i run a 64 bit kernel on all my intel hardware. it's easier to
concentrate on one kernel, and even on machines with only 4g
of memory, memory remapped above 4g to make room for
mmio like pci will be otherwise wasted. up to 1g of memory
can be remapped.
i find it very useful to launch many large processes on cpu servers.
it's really nice to have 15gb of buffers on the file server
(with only 15 page table entries!)
- erik
next prev parent reply other threads:[~2014-08-10 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 0:44 kokamoto
2014-08-09 1:25 ` cinap_lenrek
2014-08-09 3:20 ` kokamoto
2014-08-10 14:44 ` erik quanstrom [this message]
2014-08-11 0:12 ` kokamoto
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=44018b84589bc1bce1c713f6c7d2a350@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).