From: Anthony Martin <ality@pbrane.org>
To: 9fans@9fans.net
Subject: Re: [9fans] A heartfelt thanks... :-)
Date: Fri, 6 Jan 2017 01:34:14 -0800 [thread overview]
Message-ID: <20170106093414.GA26942@alice> (raw)
In-Reply-To: <CAHL7psGFWEehRF-NUHjB8hfo75SCr=yBP2kZ9dve5AY8BpowjQ@mail.gmail.com>
Ciao Giacomo,
Why did you choose to create devself? Everything it does seems
better suited to devproc. If I was going that route, I'd instead
create a QTDIR file in devproc called #p/self that is just another
view into #p/$pid. Then brk and chdir would be control messages
written to #p/self/ctl. Same with seg^(attach detach free). You
could also make those be control messages written to #p/self/segment
instead.
Also, I think it's a mistake to overload the return value of the
remove system call for passing arbitrary integers out of the kernel.
I understand why you want something like that, however. Moving
system calls into reads and writes of various files increases the
number of context switches since you have to open and close the
files. Why not do exactly what you want and make a new system
called readint or something?
Oh, and where are the man pages? /doc/hacking is missing. I'm
interested in reading about your awake system call and the changes
you've made to rendezvous and the variuos locks in libc.
Cheers,
Anthony
next prev parent reply other threads:[~2017-01-06 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 3:17 Giacomo Tesio
2017-01-06 9:34 ` Anthony Martin [this message]
2017-01-06 19:42 ` Giacomo Tesio
2018-11-16 2:03 ` Giacomo Tesio
2018-11-16 21:34 ` Ethan Gardener
2018-11-16 23:35 ` Giacomo Tesio
2018-11-17 17:18 ` Ethan Gardener
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=20170106093414.GA26942@alice \
--to=ality@pbrane.org \
--cc=9fans@9fans.net \
/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).