From: David Ahern <dsahern@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Martin KaFai Lau <kafai@fb.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Steven Rostedt <rostedt@goodmis.org>,
Lawrence Brakmo <brakmo@fb.com>, Josef Bacik <jbacik@fb.com>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [RFC PATCH net-next 0/5] tcp: TCP tracer
Date: Wed, 17 Dec 2014 13:56:33 -0700 [thread overview]
Message-ID: <5491EE01.5020406@gmail.com> (raw)
In-Reply-To: <CAADnVQ+zkNL9sJhJuAiQ_y4bis=Sck5pzG86qccXE9vvM0-drQ@mail.gmail.com>
On 12/17/14 1:42 PM, Alexei Starovoitov wrote:
>> It is not strictly necessary to carry vmlinux, that is just a probe
>> >point resolution time problem, solvable when generating a shell script,
>> >on the development machine, to insert the probes.
> on N development machines with kernels that
> would match worker machines...
> I'm not saying it's impossible, just operationally difficult.
> This is my understanding of Martin's use case.
>
That's the use case I am talking about ... N-different kernel versions
and the probe definitions would need to be generated at *build* time of
the kernel that uses a cross-compile environment. ie., can't assume
there is a development machine running the kernel from which you can
generate the probe definitions. This gets messy quick for embedded
deployments.
David
next prev parent reply other threads:[~2014-12-17 20:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:42 [RFC PATCH net-next 0/5] tcp: TCP tracer Alexei Starovoitov
2014-12-17 20:56 ` David Ahern [this message]
2014-12-17 21:24 ` Arnaldo Carvalho de Melo
2014-12-17 21:19 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2014-12-17 17:14 Alexei Starovoitov
2014-12-17 19:51 ` Arnaldo Carvalho de Melo
2014-12-17 3:06 Alexei Starovoitov
2014-12-17 21:42 ` Josef Bacik
2014-12-18 23:43 ` Lawrence Brakmo
2014-12-19 1:42 ` Yuchung Cheng
2014-12-17 0:15 Alexei Starovoitov
2014-12-17 1:30 ` Martin Lau
2014-12-15 6:55 Alexei Starovoitov
2014-12-15 16:03 ` Eric Dumazet
2014-12-15 16:08 ` Blake Matheny
2014-12-15 19:56 ` Yuchung Cheng
2014-12-17 20:45 ` rapier
2014-12-16 18:28 ` Martin Lau
2014-12-15 16:42 ` Josef Bacik
2014-12-15 22:01 ` Tom Herbert
2014-12-15 22:17 ` rapier
2014-12-15 22:29 ` Steven Rostedt
2014-12-15 23:28 ` Jamal Hadi Salim
2014-12-15 23:40 ` Eric Dumazet
2014-12-16 22:40 ` Jason Baron
2014-12-16 22:45 ` David Miller
2014-12-16 22:50 ` Hannes Frederic Sowa
2014-12-17 15:07 ` Arnaldo Carvalho de Melo
2014-12-15 1:56 Martin KaFai Lau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5491EE01.5020406@gmail.com \
--to=dsahern@gmail.com \
--cc=Kernel-team@fb.com \
--cc=alexei.starovoitov@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=brakmo@fb.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbacik@fb.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.