9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] mycroftiv's zrv and rfork V, patch for current 9front
Date: Wed, 06 Jan 2021 20:05:50 +0100	[thread overview]
Message-ID: <4FD99002DC7ADF798DF538CA33F26565@felloff.net> (raw)
In-Reply-To: <A8A041D340B90243B3E3F309BCD9A084@sirjofri.de>

this implementation seemes flawed to me.

closesgrp() appears only to free the memory of the Srv*
nodes, but doesnt actually free srv->chan, srv->owner
and srv->name.

also the locking seems suspicious. as the global Srv*
list was just replaced with per process one, but we'r
still only have a single srvlock to serialize
concurrent access to it.

so far, the srvgrp can only be reset or shared depending
of the RFCSRVG flag. once you implement copying you'd
need a lock per Sgrp. i'd prefer to have a lock per
Sgrp right now and remove the global srvlock.

pexit() should move the sgrp = up->sgrp; up->sgrp = nil
in the exiting qlock(&up->debug);... block instead of
making its own.

why do we need /zrv? is there a new devzrv.c device that
was missing in the diff?

--
cinap

  reply	other threads:[~2021-01-06 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 10:17 sirjofri+ml-9front
2021-01-06 19:05 ` cinap_lenrek [this message]
2021-01-06 19:11   ` ori
2021-01-06 20:02     ` sirjofri
2021-01-06 22:28       ` cinap_lenrek
2021-01-07 20:55         ` Stuart Morrow
2021-01-07 14:04       ` sirjofri+ml-9front
2021-01-07  1:12     ` [9front] happy new year cinap_lenrek

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=4FD99002DC7ADF798DF538CA33F26565@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --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).