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: Re: [9fans] 9p fids and references
Date: Fri, 31 Jul 2009 10:45:29 +0200	[thread overview]
Message-ID: <138575260907310145i38305c65u248324bb4af5c72c@mail.gmail.com> (raw)
In-Reply-To: <df49a7370907300901y4286671cj65dc76d7dfbd5c42@mail.gmail.com>

OK, thanks.

2009/7/30, roger peppe <rogpeppe@gmail.com>:
> 2009/7/30 hugo rivera <uair00@gmail.com>:
>  > [...] 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?
>
>
> no, because a file can be opened several times.
>  when you open a file you get a new fid.
>
>  so if you've got resources associated with the file,
>  as opposed to resources private to the fid,
>  you have to reference count them (or poison any
>  fids that point to the file, if you *really* want the
>  resource to go away)
>
>


--
Hugo



      reply	other threads:[~2009-07-31  8:45 UTC|newest]

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

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=138575260907310145i38305c65u248324bb4af5c72c@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).