9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] lguest fixed
Date: Thu,  3 Jul 2008 10:07:00 -0700	[thread overview]
Message-ID: <13426df10807031007s720fd842s9bd9b75f9a9d76b2@mail.gmail.com> (raw)

I got annoyed with the idea of lguest being broken, I was stuck on a
long flight, so I redid l.s and fixed it. The new l.s has the
improvements from sources, mainly the 8M pte map instead of the
earlier 4M pte map.

it's also seriously cleaned up to take into account the new lguest
improvements (dare I say "churn"?) which are, after all, a good thing,
since you  now start in low memory and can set up the high memory page
tables correctly for the MACH structure.

OK, could some of you with the loopback 9vx device time something for me?

on 9vx, I have a venti and fossil in the file system. hence:

index main
isect /usr/rminnich/disks/index
arenas /usr/rminnich/disks/arenas
bloom /usr/rminnich/disks/bloom
httpaddr tcp!*!8008
mem 10M
bcmem 20M
icmem 30M

fsys main config /usr/rminnich/disks/fossil
fsys main open -AWP
fsys main
create /active/adm adm sys d775
create /active/adm/users adm sys 664
users -w
srv -p fscons
srv fossil


mk clean is 3 minutes on 9vx, 20 seconds on lguest.

mk 'CONF=pccpuf' is 7 minutes on 9vx, 2:40 on lguest

Of course, xen on a slower box beats them all, at 12 seconds, so it's
not like I'm saying lguest is fast. I need to try kvm next. But I'd
be curious to see times on the 9vx /dev/sd. I will be surprised if it
makes a huge difference but I'm often surprised.

Thanks

ron



             reply	other threads:[~2008-07-03 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 17:07 ron minnich [this message]
2008-07-04 16:16 ` sqweek
2008-07-04 16:37   ` ron minnich

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=13426df10807031007s720fd842s9bd9b75f9a9d76b2@mail.gmail.com \
    --to=rminnich@gmail.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).