* Re: netlink vs. debugfs (was Re: [Patch 0/6] statistics infrastructure)
[not found] ` <4471FE52.8090107@am.sony.com>
@ 2006-05-22 18:34 ` Balbir Singh
2006-05-22 18:53 ` Evgeniy Polyakov
0 siblings, 1 reply; 2+ messages in thread
From: Balbir Singh @ 2006-05-22 18:34 UTC (permalink / raw)
To: Tim Bird; +Cc: Andrew Morton, Martin Peschke, linux-kernel, netdev
On Mon, May 22, 2006 at 11:09:22AM -0700, Tim Bird wrote:
> Andrew Morton wrote:
> > Martin Peschke <mp3@de.ibm.com> wrote:
> >> My patch series is a proposal for a generic implementation of statistics.
> >
> > This uses debugfs for the user interface, but the
> > per-task-delay-accounting-*.patch series from Balbir creates an extensible
> > netlink-based system for passing instrumentation results back to userspace.
> >
> > Can this code be converted to use those netlink interfaces, or is Balbir's
> > approach unsuitable, or hasn't it even been considered, or what?
>
> Can someone give me the 20-second elevator pitch on why
> netlink is preferred over debugfs? I've heard of a
> number of debugfs/procfs users requested to switch over.
>
> Thanks,
> -- Tim
>
> =============================
> Tim Bird
> Architecture Group Chair, CE Linux Forum
> Senior Staff Engineer, Sony Electronics
> =============================
Hi, Tim,
I am no debugfs expert, I hope I can do justice to the comparison.
Debugfs Netlink/Genetlink
1. Filesystem based - requires creating Several types of data can
files for each type of data passed be multiplexed over one netlink
down socket.
2. Hard to determine record format/data Contains metadata including
type of data and length
with each record
3. Notifications are hard Notifications are very easy
I think they can be done using inotify good library support for
notifications. Data can
either be broadcast or
selectively mulitcast
4. Requires several open/read/write/close A single socket can be
operations opened, data from kernel
space can be multiplexed
over it.
I don't think I did any justice to the advantages of debugfs. The only
one I can think of is that it uses relayfs. Relayfs is efficient in the
sense that it uses per-cpu buffers.
Anybody else want to take a shot in comparing the two?
Balbir Singh,
Linux Technology Center,
IBM Software Labs
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: netlink vs. debugfs (was Re: [Patch 0/6] statistics infrastructure)
2006-05-22 18:34 ` netlink vs. debugfs (was Re: [Patch 0/6] statistics infrastructure) Balbir Singh
@ 2006-05-22 18:53 ` Evgeniy Polyakov
0 siblings, 0 replies; 2+ messages in thread
From: Evgeniy Polyakov @ 2006-05-22 18:53 UTC (permalink / raw)
To: Balbir Singh
Cc: Tim Bird, Andrew Morton, Martin Peschke, linux-kernel, netdev
On Tue, May 23, 2006 at 12:04:00AM +0530, Balbir Singh (balbir@in.ibm.com) wrote:
> Anybody else want to take a shot in comparing the two?
Netlink is always presented in the kernel, so no need to make
additional dependencies for special FS.
But number of netlink sockets is not that big, so use new one if you
create really generic mechanism, or consider using connector/gennetlink.
--
Evgeniy Polyakov
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-05-22 18:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1148054876.2974.10.camel@dyn-9-152-230-71.boeblingen.de.ibm.com>
[not found] ` <20060519092411.6b859b51.akpm@osdl.org>
[not found] ` <4471FE52.8090107@am.sony.com>
2006-05-22 18:34 ` netlink vs. debugfs (was Re: [Patch 0/6] statistics infrastructure) Balbir Singh
2006-05-22 18:53 ` Evgeniy Polyakov
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).