From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Fwd: lib9p: Add clunk callback to Srv struct
Date: Mon, 1 Feb 2016 23:03:23 +0100 [thread overview]
Message-ID: <e319f3956f8e37d37bc2d2ecb5e272de@felloff.net> (raw)
In-Reply-To: <CAEDK68av9j-vRwY0_J8bgzs2mVsvW-zFO1+2pWcc8zAwsmbUpA@mail.gmail.com>
> Is there a reason why lib9p doesn't have a clunk function pointer in Srv struct?
what about Srv.destroyfid()?
Destroyfid
When a Fid's reference count drops to zero (i.e., it
has been clunked and there are no outstanding requests
referring to it), destroyfid is called to allow the
program to dispose of the fid->aux pointer.
--
cinap
next prev parent reply other threads:[~2016-02-01 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEDK68Ze=Di=8qQt1GOfkhq9nxb29=q=Z+AUuxzJouOT6_WeTg@mail.gmail.com>
2016-02-01 21:54 ` Tiago Natel
2016-02-01 22:03 ` cinap_lenrek [this message]
2016-02-02 18:17 ` Tiago Natel
2016-02-02 19:15 ` Skip Tavakkolian
2016-02-03 1:25 ` cinap_lenrek
2016-02-03 11:53 ` Tiago Natel
2016-02-01 22:42 ` Skip Tavakkolian
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=e319f3956f8e37d37bc2d2ecb5e272de@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).