From: Nick Piggin <npiggin@suse.de>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: David VomLehn <dvomlehn@cisco.com>,
to@dvomlehn-lnx2.corp.sa.net, netdev@vger.kernel.org
Subject: Re: [PATCH][RFC] Infrastructure for compact call location representation
Date: Wed, 9 Jun 2010 18:44:17 +1000 [thread overview]
Message-ID: <20100609084417.GW26335@laptop> (raw)
In-Reply-To: <20100608084456.4da00349@nehalam>
On Tue, Jun 08, 2010 at 08:44:56AM -0700, Stephen Hemminger wrote:
> On Mon, 7 Jun 2010 17:30:52 -0700
> David VomLehn <dvomlehn@cisco.com> wrote:
> > History
> > v2 Support small callsite IDs and split out out-of-band parameter
> > parsing.
> > V1 Initial release
> >
> > Signed-off-by: David VomLehn <dvomlehn@cisco.com>
>
> This is really Linux Kernel Mailing List material (not just netdev). And it will
> be a hard sell to get it accepted, because it is basically an alternative call
> tracing mechanism, and there are already several of these in use or under development
> (see perf and ftrace).
What about a generic extension or layer on top of stacktrace that
does caching and unique IDs for stack traces. This way you can get
callsites or _full_ stack traces if required, and it shouldn't require
any extra magic in the net functions.
You would need a hash for stack traces to check for an existing trace,
and an idr to assign ids to traces.
next prev parent reply other threads:[~2010-06-09 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 0:30 [PATCH][RFC] Infrastructure for compact call location representation David VomLehn
2010-06-08 15:44 ` Randy Dunlap
2010-06-08 18:59 ` David VomLehn
2010-06-08 15:44 ` Stephen Hemminger
2010-06-08 19:06 ` David VomLehn
2010-06-09 8:44 ` Nick Piggin [this message]
2010-06-09 18:22 ` David VomLehn
2010-06-10 8:47 ` Nick Piggin
2010-06-09 7:17 ` Andi Kleen
2010-06-09 18:13 ` David VomLehn
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=20100609084417.GW26335@laptop \
--to=npiggin@suse.de \
--cc=dvomlehn@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=to@dvomlehn-lnx2.corp.sa.net \
/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.