From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Philipp Reh <sefi@s-e-f-i.de>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: When does Linux drop UDP packets?
Date: Thu, 04 Jun 2009 23:16:16 +0530 [thread overview]
Message-ID: <1244137576.3553.3.camel@ht.satnam> (raw)
In-Reply-To: <alpine.DEB.2.00.0906041228170.14994@gandalf.stny.rr.com>
On Thu, 2009-06-04 at 12:34 -0400, Steven Rostedt wrote:
> BTW, I used ftrace to look into this:
>
> Enable:
>
> CONFIG_FTRACE
> CONFIG_FUNCTION_TRACER
> CONFIG_FUNCITON_GRAPH_TRACER
> CONFIG_DYNAMIC_FTRACE
>
> Compile and boot:
>
> # mount -t debugfs nodev /sys/kernel/debug
Very glad to see you following standards ;-)
> # cd /sys/kernel/debug
hmm you mean # cd /sys/kernel/debug/tracing
> # echo udp_rcv > set_graph_function
> # echo function_graph > current_tracer
> # cat trace
>
Anyway you can also see UDP packet drops when you increase network and
CPU load.
--
JSR
next prev parent reply other threads:[~2009-06-04 17:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 14:53 When does Linux drop UDP packets? Philipp Reh
2009-06-04 15:57 ` Steven Rostedt
[not found] ` <20090604161015.GA17303@miyuki>
[not found] ` <alpine.DEB.2.00.0906041222450.14994@gandalf.stny.rr.com>
2009-06-04 16:34 ` Steven Rostedt
2009-06-04 16:57 ` Steven Rostedt
2009-06-04 17:46 ` Jaswinder Singh Rajput [this message]
2009-06-04 21:07 ` Steven Rostedt
2009-06-04 17:57 ` david
2009-06-04 18:44 ` Eric Dumazet
2009-06-04 18:49 ` david
2009-06-11 23:40 ` Nifty niftylinkern Mitch
2009-06-04 22:03 ` Alexander Clouter
2009-06-04 23:19 ` david
2009-06-05 19:10 ` Alexander Clouter
2009-06-05 19:15 ` david
2009-06-05 19:29 ` Alexander Clouter
2009-06-24 7:47 ` Herbert Xu
2009-06-25 4:32 ` david
2009-06-25 5:00 ` Herbert Xu
2009-06-25 5:37 ` david
2009-06-25 6:13 ` Herbert Xu
2009-06-25 7:38 ` Alexander Clouter
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=1244137576.3553.3.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sefi@s-e-f-i.de \
/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.