Re: [RFC PATCH 0/3] A couple of feature requests to the unifiedtrace buffer

From: Steven Rostedt
Date: Tue Dec 02 2008 - 22:46:46 EST



On Tue, 2008-12-02 at 19:35 -0800, Jiaying Zhang wrote:

> > If you check out my git tree:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> >
> > branch: tip/devel
> >
> > You will see that I started writing code to handle "splice". I have a
> > retarded version that works right now (using the term "works" loosely
> > here).
>
> This is great! I just checked out your git tree and will take a close look.
> Do you plan to support mmap other than splice in the unified trace buffer?
> I am not familiar with splice. Is it superior?
>
> >
> > Also, most of our development is done in the Ingo's tip tree:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
> >
> > branch: master
> >
> > I see in the patches that you based this on 2.6.26.2? Not sure which
> > version of the ring buffer you are using, but there has been lots of
> > improvements to it already.
>
> My patches are based on the unified ring buffer code I checked out
> from git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
> a week ago. I saw you posted two new patches today. I haven't merged
> my patches with them yet.

OK, I was nervous by seeing in your patches:

Index: linux-2.6.26.2/include/asm-generic/vmlinux.lds.h
===================================================================
--- linux-2.6.26.2.orig/include/asm-generic/vmlinux.lds.h
2008-11-25 11:32:26.000000000 -0800
+++ linux-2.6.26.2/include/asm-generic/vmlinux.lds.h 2008-11-25


My splice code is not in git yet. I can put it there tonight. But the
ring buffer code needed to work with splice is there. The splice work is
at the ftrace level, but you probably could use the same as well.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/