From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: Re: [9front] hack-a-thon daily proceedings summaries
Date: Thu, 11 Aug 2022 05:15:04 -0700 [thread overview]
Message-ID: <YvTyyFzWtzPoOHIW@alice> (raw)
In-Reply-To: <E2E9D5F26897160C610D21DB8AFC8D51@eigenstate.org>
ori@eigenstate.org once said:
> 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.
I thought the ps interface from 9k/nix/9exp was pretty good.
It would let you play around with different process allocation
schemes without churn in port/^(devproc.c edf.c proc.c) etc.
https://bitbucket.org/forsyth/plan9-9exp/src/master/sys/src/9exp/port/ps.c
Cheers,
Anthony
next prev parent reply other threads:[~2022-08-11 12:17 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
2022-08-11 12:15 ` Anthony Martin [this message]
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=YvTyyFzWtzPoOHIW@alice \
--to=ality@pbrane.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).