public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, shemminger@vyatta.com
Subject: Re: [PATCH] IP: Increment INADDRERRORS if routing for a packet is not successful
Date: Wed, 02 Jun 2010 18:33:59 +0200	[thread overview]
Message-ID: <1275496439.2725.203.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1006021126500.30182@router.home>

Le mercredi 02 juin 2010 à 11:27 -0500, Christoph Lameter a écrit :
> On Wed, 2 Jun 2010, David Miller wrote:
> 
> > From: Christoph Lameter <cl@linux-foundation.org>
> > Date: Wed, 2 Jun 2010 11:12:14 -0500 (CDT)
> >
> > > Its important to know why drops occur (any drops for that matter, drops
> > > mean retransmit which means latency).
> >
> > We know, that's why there is a networking tracepoint that allows you
> > to see where all drops occur. :-)
> 
> Where can I find out more about the network tracepoint?
> 

take a look at 

http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/html/SystemTap_Beginners_Guide/useful-systemtap-scripts.html#dropwatch




  reply	other threads:[~2010-06-02 16:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 21:13 [PATCH] IP: Increment INADDRERRORS if routing for a packet is not successful Christoph Lameter
2010-06-01 22:07 ` Eric Dumazet
2010-06-01 22:23   ` David Miller
2010-06-02 15:27   ` Christoph Lameter
2010-06-02 15:29     ` David Miller
2010-06-02 15:32     ` Eric Dumazet
2010-06-02 16:12       ` Christoph Lameter
2010-06-02 16:19         ` David Miller
2010-06-02 16:27           ` Christoph Lameter
2010-06-02 16:33             ` Eric Dumazet [this message]
2010-06-02 16:49               ` Christoph Lameter
2010-06-02 17:12                 ` David Miller
2010-06-02 17:19                   ` Eric Dumazet
2010-06-02 17:41                     ` Neil Horman
2010-06-02 17:31                   ` David Miller
2010-06-02 17:46                     ` Eric Dumazet
2010-06-02 18:01                       ` Christoph Lameter
2010-06-02 18:41                         ` Eric Dumazet
2010-06-02 18:59                           ` Christoph Lameter
2010-06-02 19:25                             ` Eric Dumazet
2010-06-02 20:11                               ` Christoph Lameter
2010-06-02 22:05                                 ` [PATCH net-next-2.6] ipv4: add LINUX_MIB_IPRPFILTER snmp counter Eric Dumazet
2010-06-03 10:19                                   ` David Miller
2010-06-03  3:50                     ` [PATCH] IP: Increment INADDRERRORS if routing for a packet is not successful Bill Fink
2010-06-03  3:54                       ` Eric Dumazet
2010-06-03  4:56                         ` Bill Fink
2010-06-02 16:28         ` Eric Dumazet
2010-06-02 16:35           ` Christoph Lameter

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=1275496439.2725.203.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox