From: Marcelo Ricardo Leitner <mleitner@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Rick Jones <rick.jones2@hp.com>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Yuchung Cheng <ycheng@google.com>,
Matt Mathis <mattmathis@google.com>,
Craig Gallek <cgallek@google.com>, Martin Lau <kafai@fb.com>,
Chris Rapier <rapier@psc.edu>
Subject: Re: [PATCH net-next] tcp: add tcpi_segs_in and tcpi_segs_out to tcp_info
Date: Thu, 21 May 2015 09:38:45 -0300 [thread overview]
Message-ID: <20150521123845.GQ2298@localhost.localdomain> (raw)
In-Reply-To: <1432169554.4060.71.camel@edumazet-glaptop2.roam.corp.google.com>
On Wed, May 20, 2015 at 05:52:34PM -0700, Eric Dumazet wrote:
> On Wed, 2015-05-20 at 17:48 -0700, Rick Jones wrote:
> > On 05/20/2015 05:37 PM, Eric Dumazet wrote:
> >
> > > Anyway, if we can send tcp data at 100Gbits on one flow, I guess we are
> > > doing a terrific job and do not need to tweak TCP stack anymore ;)
> >
> > :)
> >
>
> Note that I have no particular strong feelings with these counters being
> 32 or 64bits. Its adding 8 extra bytes and a bit more overhead, nothing
> more.
And if they really need an absolute number, 500s is still pretty much
enough for polling these and adding the delta to some local u64 var.
Marcelo
next prev parent reply other threads:[~2015-05-21 12:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 22:28 [PATCH v2 net-next 0/2] tcp: tcp_info extensions Eric Dumazet
2015-04-28 22:28 ` [PATCH v2 net-next 1/2] tcp: add tcpi_bytes_acked to tcp_info Eric Dumazet
2015-04-29 22:12 ` David Miller
2015-04-28 22:28 ` [PATCH v2 net-next 2/2] tcp: add tcpi_bytes_received " Eric Dumazet
2015-04-28 22:56 ` Yuchung Cheng
2015-04-28 23:07 ` Eric Dumazet
2015-04-29 22:12 ` David Miller
2015-05-12 13:08 ` [PATCH v2 net-next 0/2] tcp: tcp_info extensions Marcelo Ricardo Leitner
2015-05-12 20:31 ` Eric Dumazet
2015-05-12 22:21 ` Marcelo Ricardo Leitner
2015-05-20 23:35 ` [PATCH net-next] tcp: add tcpi_segs_in and tcpi_segs_out to tcp_info Eric Dumazet
2015-05-21 0:06 ` Rick Jones
2015-05-21 0:37 ` Eric Dumazet
2015-05-21 0:48 ` Rick Jones
2015-05-21 0:52 ` Eric Dumazet
2015-05-21 12:38 ` Marcelo Ricardo Leitner [this message]
2015-05-21 19:41 ` Yuchung Cheng
2015-05-21 20:06 ` Eric Dumazet
2015-05-21 21:53 ` Marcelo Ricardo Leitner
2015-05-22 3:25 ` David Miller
2015-05-22 3:43 ` Eric Dumazet
2015-05-22 4:51 ` [PATCH net-next] tcp: fix a potential deadlock in tcp_get_info() Eric Dumazet
2015-05-22 17:50 ` David Miller
2015-05-22 17:56 ` Eric Dumazet
2015-05-22 18:03 ` Eric Dumazet
2015-05-22 18:08 ` Eric Dumazet
2015-05-22 18:21 ` David Miller
2015-05-22 18:12 ` David Miller
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=20150521123845.GQ2298@localhost.localdomain \
--to=mleitner@redhat.com \
--cc=cgallek@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kafai@fb.com \
--cc=mattmathis@google.com \
--cc=netdev@vger.kernel.org \
--cc=rapier@psc.edu \
--cc=rick.jones2@hp.com \
--cc=ycheng@google.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