9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] 9p fids and references
Date: Thu, 30 Jul 2009 17:25:12 +0200	[thread overview]
Message-ID: <138575260907300825p4b005c50o990df6ff2a0c68cc@mail.gmail.com> (raw)

Hi,
I am trying to implement a toy fs using the 9p protocol. I've been
reading Francisco's intro to plan 9 and section 5 of the manual pages,
and I have to say I am surprised because I am actually learning from
them; plan 9 man pages are really readable :-) (not to mention
Francisco's fine intro).
Anyway, there's one thing unclear for me and it's about fids and
references: when a client opens a connection to my server, it chooses
fids for all the files I have inside and also navigates the fs and
performs operations using these fids (which are somehow mapped to qids
in my server, but this isn't cristal clear for me; tough I know qids
are unique and fids not necessarily so). The Fid structure contains an
aux pointer to whatever I want and I am using it, but my problems
start when I want to get rid of the data pointed by aux. In my fs,
it's guaranteed that each file points to its unique data structure
(pointed by aux) and there's no way two different files point to the
same data structure (but maybe two different fids do?) so reference
counting is unnecessary, am I right? I believe that clone shouldn't be
a problem since I am creating copies of the structure instead of
passing just a reference.
I am trying to avoid dangling pointers when a file is removed without
using reference counting, is it possible?
Saludos

--
Hugo



             reply	other threads:[~2009-07-30 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 15:25 hugo rivera [this message]
2009-07-30 16:01 ` roger peppe
2009-07-31  8:45   ` hugo rivera

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=138575260907300825p4b005c50o990df6ff2a0c68cc@mail.gmail.com \
    --to=uair00@gmail.com \
    --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).