On Sat, Jun 21, 2008 at 06:03:42PM +1000, Ben Nizette wrote:
quoted text
> In the kobject/kset case the separation makes sense as kobjects are
> embedded in things all over the kernel controlling things like ref
> counting, device model glue, hotplug info as well as the sysfs
> representation.  The config_item doesn't have any responsibilities
> outside of the configfs representation (does it?) so the analogy isn't
> 100%.  Though of course the item/group split makes sense if there are
> grander plans for the config_item in the future.

	The config_item is indeed embedded in whatever struct it maps
too.  eg, the ocfs2 nodemanager can have a couple hundred nodes, and
that's one config_item per.  The fs/dlm stuff can have even more nodes.

Joel

-- 

Life's Little Instruction Book #222

	"Think twice before burdening a friend with a secret."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/