From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ken's fs
Date: Thu, 25 Oct 2007 13:03:37 -0400 [thread overview]
Message-ID: <29cfe3e0d5607077f79b6575e17ee4e6@coraid.com> (raw)
In-Reply-To: <cea5682bf0ef3a7505b4c109b5abc692@coraid.com>
> i refreshed my copy on sources (/n/sources/contrib/quanstro/src/myfs).
> if used with /n/sources/contrib/quanstro/9loadaoe, it will recognize
> the results of the e820 scan. my machine reports,
> found 1 e820 memory banks 3326MB+13056MB
> topofmem = cfc00000
> cpuiddx bfebfbff
> pse: yes
> (which is good, because the fs set up just this spring is averaging
>
> the e820 scan is done from l.s so if you copy the #include "real820.s"
> line from that l.s, you can use it in any other 9load.
> but 9loadaoe has a few advantages. it's a little more forgiving of packets
> arriving at the wrong time, a little better with multiple interfaces and
> will allow one to boot from aoe storage.
>
> - erik
cut and paste error
should read:
i refreshed my copy on sources (/n/sources/contrib/quanstro/src/myfs).
if used with /n/sources/contrib/quanstro/9loadaoe, it will recognize
the results of the e820 scan. my new fs reports 3326 MB of memory
below 4GB.
the e820 scan is done from l.s so if you copy the #include "real820.s"
line from that l.s and real820.s, you can use it other versions of 9load.
but 9loadaoe has a few advantages. it's a little more forgiving of packets
arriving at the wrong time, a little better with multiple interfaces and
will allow one to boot from aoe storage.
- erik
prev parent reply other threads:[~2007-10-25 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 16:34 erik quanstrom
2007-10-25 17:03 ` erik quanstrom [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=29cfe3e0d5607077f79b6575e17ee4e6@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).