From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] hack-a-thon daily proceedings summaries
Date: Mon, 08 Aug 2022 10:05:51 -0400 [thread overview]
Message-ID: <E2E9D5F26897160C610D21DB8AFC8D51@eigenstate.org> (raw)
In-Reply-To: <YvEE30XHRWPLpS6W@alice>
Quoth Anthony Martin <ality@pbrane.org>:
>
> What is he moving out of struct Proc? An additional indirection
> for infrequently used fields or the error buffers and maybe moving
> to bit-flags for some of the ints used as booleans? Ori, show us
> your portdat.h. ☺
Current status is just understanding what data structures need to
change to allow runtime growth; there are a bunch of rarely used
buffers like error state that can be moved out, but I'm less worried
about sizeof(Proc) than removing direct indexes to proctab.
next prev parent reply other threads:[~2022-08-08 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 5:43 smj
2022-08-08 10:15 ` hiro
2022-08-08 12:43 ` Anthony Martin
2022-08-08 13:25 ` hiro
2022-08-08 14:05 ` ori [this message]
2022-08-11 12:15 ` Anthony Martin
2022-08-11 14:37 ` hiro
2022-08-08 19:55 ` qwx
2022-08-08 20:07 ` Marshall Conover
2022-08-09 9:15 ` hiro
2022-08-16 21:17 ` ori
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=E2E9D5F26897160C610D21DB8AFC8D51@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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).