[lkml]   [2005]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.11-rc1-mm1
Andrew Morton wrote:
> - Added the Linux Trace Toolkit (and hence relayfs). Mainly because I
> haven't yet taken as close a look at LTT as I should have. Probably neither
> have you.
> It needs a bit of work on the kernel<->user periphery, which is not a big
> deal.
> As does relayfs, IMO. It seems to need some regularised way in which a
> userspace relayfs client can tell relayfs what file(s) to use. LTT is
> currently using some ghastly stick-a-pathname-in-/proc thing. Relayfs
> should provide this service.
> relayfs needs a closer look too. A lot of advanced instrumentation
> projects seem to require it, but none of them have been merged. Lots of
> people say "use netlink instead" and lots of other people say "err, we think
> relayfs is better". This is a discussion which needs to be had.

Thanks very much. I know lots of embedded folks who will be happy to
see this discussion take place. (As an aside, I'll try to encourage
some of our more shy members to speak up and participate in the
discussion as well. I know Hitachi has been doing some work on
tracing, and I'd hate to see duplicate effort.)

BTW - I agree with most of the relayfs comments. It seems like overkill
for the kernel developer doing a "casual", ad-hoc trace. I'll try to
work with Karim on the suggested improvements.

Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:09    [W:0.371 / U:0.892 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site