On 05/12/10 04:58 AM, [email protected] wrote:
Roland Mainz<[email protected]> wrote:
The sharefs system call would be changed to accept: a protocol discriminator
(NFS or SMB), an operation (publish or unpublish) and an opaque pointer to
share data. The opaque data passes transparently through sharefs between
the protocol-specific libshare plugin and the protocol service per PSARC
2010/124. The new prototype for sharefs would be of the form:
int sharefs(sharefs_proto_t proto, sharefs_op_t opcode,
void *data, size_t datalen);
Please do me a small favour and add a flags field, e.g. turn this
prototype into:
-- snip --
int sharefs(sharefs_proto_t proto, sharefs_op_t opcode,
void *data, size_t datalen, uint32_t flags);
-- snip --
The idea is that future consumers (e.g. AFS etc.) can use this for
_easy_ extensions without having to change this API again (and please
don't say this is not needed - see |fork()| vs. |forkx()|).
Why do you believe, flags cannot be put into the "data" structure if really
needed?
Its a moot point. The API is private between the kernel and library,
and thus can evolve in whatever way is necessary in the future without
impacting other software.
- Garrett
_______________________________________________
opensolaris-arc mailing list
[email protected]
