From: Lars Marowsky-Bree <lmb@suse.de>
To: linux clustering <linux-cluster@redhat.com>,
"Walker, Bruce J (HP-Labs)" <bruce.walker@hp.com>,
David Teigland <teigland@redhat.com>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
clusters_sig@lists.osdl.org
Subject: Re: [Clusters_sig] RE: [Linux-cluster] Re: [Ocfs2-devel] [RFC] nodemanager, ocfs2, dlm
Date: Fri, 22 Jul 2005 01:22:35 +0200 [thread overview]
Message-ID: <20050721232235.GJ24464@marowsky-bree.de> (raw)
In-Reply-To: <20050720183938.GM16618@ca-server1.us.oracle.com>
On 2005-07-20T11:39:38, Joel Becker <Joel.Becker@oracle.com> wrote:
> In turn, let me clarify a little where configfs fits in to
> things. Configfs is merely a convenient and transparent method to
> communicate configuration to kernel objects. It's not a place for
> uevents, for netlink sockets, or for fancy communication. It allows
> userspace to create an in-kernel object and set/get values on that
> object. It also allows userspace and kernelspace to share the same
> representation of that object and its values.
> For more complex interaction, sysfs and procfs are often more
> appropriate. While you might "configure" all known nodes in configfs,
> the node up/down state might live in sysfs. A netlink socket for
> up/down events might live in procfs. And so on.
Right. Thanks for the clarification and elaboration, for I am sure
not entirely clear as to how all these mechanisms relate in detail and
what is appropriate just where, and when to use something more classic
like ioctl etc... ;-)
FWIW, we didn't mean to get uevents out via configfs of course.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next prev parent reply other threads:[~2005-07-21 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 16:55 [Linux-cluster] Re: [Ocfs2-devel] [RFC] nodemanager, ocfs2, dlm Walker, Bruce J (HP-Labs)
2005-07-20 18:09 ` [Clusters_sig] " Lars Marowsky-Bree
2005-07-20 18:39 ` Joel Becker
2005-07-21 23:22 ` Lars Marowsky-Bree [this message]
2005-07-22 3:22 ` Daniel Phillips
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=20050721232235.GJ24464@marowsky-bree.de \
--to=lmb@suse.de \
--cc=bruce.walker@hp.com \
--cc=clusters_sig@lists.osdl.org \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=teigland@redhat.com \
/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