[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090209132819.GA17405@hmsreliant.think-freely.org>
Date: Mon, 9 Feb 2009 08:28:19 -0500
From: Neil Horman <nhorman@...driver.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Stephen Hemminger <shemminger@...tta.com>, netdev@...r.kernel.org,
davem@...emloft.net, kuznet@....inr.ac.ru, pekkas@...core.fi,
jmorris@...ei.org, yoshfuji@...ux-ipv6.org
Subject: Re: [RFC] addition of a dropped packet notification service
On Mon, Feb 09, 2009 at 09:21:34PM +1100, Herbert Xu wrote:
> On Sat, Feb 07, 2009 at 12:49:32PM -0500, Neil Horman wrote:
> >
> > Well, as I mentioned, its totally incomplete. I only posted it, so that you
> > could see an exemplar of how I wanted to use tracepoints to dynamically
> > intercept various in kernel events so that I could gather drop notifications. Of
> > course several other tracepoints will be needed to capture other classes of drop
> > (IPv6 stats, arp queue overflows, qdisc drops, etc).
>
> FWIW it sounds pretty reasonable to me. Although I'm still unsure
> on what impact all these trace points will have on the maintainence
> of our source code.
>
I think thats a fair question, and I don't honestly know the answer. In my
projections I expect the tracepoint to only need to be placed in the
snmpv6/6/linux macros and perhaps 3 other points. I'll know more when I
complete the work, and the it can get a through review.
To address the performance questions, I'll certainly run some tests to compare
the number of jiffies a trace takes on baseline (CONFIG_TRACEPOINTS not set),
with tracepoints configured but not enabled, and with them enabled.
Thanks for the feedback.
Neil
> Cheers,
> --
> Visit Openswan at http://www.openswan.org/
> Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists