From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: SUNRPC: non-exclusive pipe creation
Date: Thu, 27 Oct 2011 22:03:04 +0400 [thread overview]
Message-ID: <4EA99CD8.2070100@parallels.com> (raw)
Hello.
I'm working on making RPC pipefs per network namespace in 3.1.kernel and I don't
understand, why pipes are created in non-exclusive mode.
IOW we create pipes only in kernel, and, as I see it, each of them have unique
name and created under unique directory name.
This code looks like obsolete and left from previous logic, which has been
replaced a while ago.
Am I right? Or I missed something?
--
Best regards,
Stanislav Kinsbursky
reply other threads:[~2011-10-27 18:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EA99CD8.2070100@parallels.com \
--to=skinsbursky@parallels.com \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).