From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] I hate to insist... (Was: Venti for Fossil)
Date: Wed, 9 Jul 2003 12:16:59 +0200 [thread overview]
Message-ID: <20030709121658.M7106@cackle.proxima.alt.za> (raw)
I appreciate that some of my previous questions may have been a little
uninformed, but now I really would like a simple answer:
In /sys/src/cmd/venti/fmtindex.c, the last section starts
addr = IndexBase;
n = 0;
...
and seemingly proceeeds to compute arena maps (amap[n]) based on the
arena size
amap[n].start = addr;
addr += ap->arenas[j]->size;
amap[n].stop = addr;
with, later:
ix->amap = amap;
Why is the start address "IndexBase" and not "ArenaBase"? And, in
my opinion, "addr" should be incremented by
ap->arenas[j]->size + 2 * ap->arenas[j]->blockSize
because ap->arenas[j]->size is generated (in arena.c:/initArena) by
arena->size = size - 2 * blockSize;
Please someone tell me where I'm going wrong!
++L
reply other threads:[~2003-07-09 10:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030709121658.M7106@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).