public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: Andrew Morton <akpm@osdl.org>,
	phillips@istop.com, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC][PATCH 1 of 4] Configfs is really sysfs
Date: Sat, 3 Sep 2005 21:41:36 -0700	[thread overview]
Message-ID: <20050904044136.GR8684@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20050904041224.GP8684@ca-server1.us.oracle.com>

On Sat, Sep 03, 2005 at 09:12:24PM -0700, Joel Becker wrote:
> On Tue, Aug 30, 2005 at 04:28:46PM -0700, Andrew Morton wrote:
> > Sure, but all that copying-and-pasting really sucks.  I'm sure there's some
> > way of providing the slightly different semantics from the same codebase?

	The final piece of similar code is the buffered I/O setup for
attribute files.  Here, the major difference is how config_items and
kobjects refer to their show/store operations.  The functions have
different rules on this.
	A kobject doesn't need show/store, it can provide one for the
entire kset or subsystem.  A config_item necessarily has one for its
type, and cannot chain up.  So somehow the code would need to know which
was the case.
	 A kobject directly has a sysfs_ops structure.  The config_item
has show/store in a config_item_operations strucutre.  If you split them
out, you add a pointer and some needless complexity.  So the different
code paths need to refer to the functions differently.
	The attribute and configfs_attribute structures are physically
identical, but the sysfs one has poor naming (IMHO).  If struct
attribute wasn't going to change, and no magic would be added to its
usage (magic like kobject_add()'s intertwining with sysfs), they could
probably be shared.

Joel

-- 

"The doctrine of human equality reposes on this: that there is no
 man really clever who has not found that he is stupid."
	- Gilbert K. Chesterson

Joel Becker
Senior Member of Technical Staff
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2005-09-04  4:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 22:54 [RFC][PATCH 1 of 4] Configfs is really sysfs Daniel Phillips
2005-08-30 22:57 ` [RFC][PATCH 2 " Daniel Phillips
2005-08-30 22:59   ` [RFC][PATCH 3 " Daniel Phillips
2005-08-30 23:03     ` [RFC][PATCH 4 " Daniel Phillips
2005-08-30 23:30       ` Daniel Phillips
2005-08-30 23:06     ` [RFC][PATCH 3 " Stephen Hemminger
2005-08-30 23:18       ` Daniel Phillips
2005-08-30 23:10     ` Daniel Phillips
2005-08-30 23:22   ` [RFC][PATCH 2 " Daniel Phillips
2005-08-30 23:13 ` [RFC][PATCH 1 " Joel Becker
2005-08-30 23:25   ` Daniel Phillips
2005-08-30 23:35     ` Daniel Phillips
2005-08-30 23:28   ` Andrew Morton
2005-08-30 23:34     ` viro
2005-08-30 23:51       ` Daniel Phillips
2005-08-30 23:37     ` Daniel Phillips
2005-08-31  0:03     ` Joel Becker
2005-09-04  3:53     ` Joel Becker
2005-09-04  4:12       ` Joel Becker
2005-09-04  4:41         ` Joel Becker [this message]
2005-09-04  4:54           ` Joel Becker
2005-09-07 20:31             ` Greg KH

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=20050904044136.GR8684@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@istop.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