| To: | Baruch Even <baruch@xxxxxxxxx> |
|---|---|
| Subject: | Re: way of figuring out total number of retransmitted packets on a TCP socket? |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Wed, 20 Oct 2004 15:16:01 -0700 |
| Cc: | buytenh@xxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <1098278702.16002.7.camel@baruch.hamilton.local> |
| References: | <20041020130134.GC24757@xi.wantstofly.org> <1098278702.16002.7.camel@baruch.hamilton.local> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Wed, 20 Oct 2004 14:25:02 +0100 Baruch Even <baruch@xxxxxxxxx> wrote: > The web100 patch gives you that, but it's not part of the basic kernel. You don't need web100 for this simple statistic, see "tcpi_retrans" We also provide nearly all of the lost packet tracking stats in the form of "tcpi_unacked", "tcpi_sacked", "tcpi_lost", and "tcpi_fackets". In fact, web100 duplicates a lot of functionality provided already by tcp_diag :-) |
| Previous by Date: | [PATCH 2.6] iptables CONNMARK match+target, Harald Welte |
|---|---|
| Next by Date: | Re: netdev-2.6 queue updated, Jeff Garzik |
| Previous by Thread: | Re: way of figuring out total number of retransmitted packets on a TCP socket?, Baruch Even |
| Next by Thread: | Re: way of figuring out total number of retransmitted packets on a TCP socket?, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |