Messages in this thread | | | Date | Fri, 4 Apr 2014 15:26:32 +0800 | Subject | Re: ktap and ebpf integration | From | Jovi Zhangwei <> |
| |
On Fri, Apr 4, 2014 at 2:26 PM, Alexei Starovoitov <ast@plumgrid.com> wrote: > On Thu, Apr 3, 2014 at 6:21 PM, Jovi Zhangwei <jovi.zhangwei@gmail.com> wrote: >> Hi Alexei, >> >> We talked a lot on ktap and ebpf integration in these days, >> Now I think we can put into deeply to thinking out some >> technical issues in there. >> >> Firstly, I want to make sure you are support this ktap and >> ebpf integration direction, I aware you have ongoing 'bpf filter' >> patch set work, which actually overlapping with ktap integration >> efforts (IMO the interface should be unified and simple for user, >> so I think filter debugfs file is not a good interface), so please let >> me know your answer about this. > > I think the more choices users have the better. > I'll continue with C based filters and you can continue with ktap > syntax. That's ok. We can share all kernel pieces.
Now I understand that there is no way to integrate ktap and ibpf in technical point of view, the kernel side and interface is completely different, and obviously you don't want to change current per-event filter file based interface and kernel part, that make impossible to let ktap could integrate or share with ibpf.
Anyway, I think there will don't have any necessary to upstream ktap any more, I still enjoy the simplicity and flexibility given by ktap, and hope there will have a kernel built-in alternative solution in future.
Specially thanks for the guys which put the efforts on ktap review.
Jovi
| |