From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 11/11] nfs-acl
Date: Mon, 26 Apr 2004 17:10:19 -0400 [thread overview]
Message-ID: <1083013819.15282.56.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1082975215.3295.81.camel@winden.suse.de>
On Mon, 2004-04-26 at 06:28, Andreas Gruenbacher wrote:
> Client nfsacl support
>
> Add support for the nfsacl protocol extension to nfs.
>
Why do we have to allocate an extra socket here? Can't we always assume
that the NFSACL server will listen on port 2049 (the same as the NFS
server)?
If so, we can simply clone the NFS rpc_client in order to share the
socket/security flavours/...
BTW: why does the client side NFS_ACL select QSORT? Can't userland do
all that for us?
Cheers,
Trond
next prev parent reply other threads:[~2004-04-26 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 10:28 Andreas Gruenbacher
2004-04-26 21:10 ` Trond Myklebust [this message]
2004-04-27 17:33 ` Andreas Gruenbacher
2004-04-27 17:54 ` Trond Myklebust
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=1083013819.15282.56.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®