From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Alexander Aring <aring@mojatatu.com>,
Tariq Toukan <tariqt@mellanox.com>,
David Miller <davem@davemloft.net>,
edumazet@google.com, netdev@vger.kernel.org, fw@strlen.de,
herbert@gondor.apana.org.au, tgraf@suug.ch, alex.aring@gmail.com,
stefan@osg.samsung.com, ktkhai@virtuozzo.com,
Moshe Shemesh <moshe@mellanox.com>,
Eran Ben Elisha <eranbe@mellanox.com>,
brouer@redhat.com, Rick Jones <rick.jones2@hpe.com>
Subject: Re: [PATCH v4 net-next 00/19] inet: frags: bring rhashtables to IP defrag
Date: Wed, 30 May 2018 11:20:22 +0200 [thread overview]
Message-ID: <20180530112022.2b793051@redhat.com> (raw)
In-Reply-To: <13bf3889-4426-b17a-d8d7-e843038a2a82@gmail.com>
On Mon, 28 May 2018 09:09:17 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Tariq, here are my test results : No drops for me.
>
> # ./netperf -H 2607:f8b0:8099:e18:: -t UDP_STREAM
> MIGRATED UDP STREAM TEST from ::0 (::) port 0 AF_INET6 to 2607:f8b0:8099:e18:: () port 0 AF_INET6
> Socket Message Elapsed Messages
> Size Size Time Okay Errors Throughput
> bytes bytes secs # # 10^6bits/sec
>
> 212992 65507 10.00 202117 0 10592.00
> 212992 10.00 0 0.00
Hmm... Eric the above result show that ALL your UDP packets were dropped!
You have 0 okay messages and 0.00 Mbit/s throughput.
It needs to look like below (test on i40e NIC):
$ netperf -t UDP_STREAM -H fee0:cafe::1
MIGRATED UDP STREAM TEST from ::0 (::) port 0 AF_INET6 to fee0:cafe::1 () port 0 AF_INET6 : histogram : demo
Socket Message Elapsed Messages
Size Size Time Okay Errors Throughput
bytes bytes secs # # 10^6bits/sec
212992 65507 10.00 186385 0 9767.08
212992 10.00 186385 9767.08
If I manually instruct ip6tables to drop all UDP packets, then I get
what you see... so, something on your test system are likely dropping
your UDP packets, but letting regular netperf (TCP) control
communication through.
# ip6tables -I INPUT -p udp -j DROP
$ netperf -t UDP_STREAM -H fee0:cafe::1
MIGRATED UDP STREAM TEST from ::0 (::) port 0 AF_INET6 to fee0:cafe::1 () port 0 AF_INET6 : histogram : demo
Socket Message Elapsed Messages
Size Size Time Okay Errors Throughput
bytes bytes secs # # 10^6bits/sec
212992 65507 10.00 182095 0 9542.41
212992 10.00 0 0.00
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-05-30 9:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 19:58 [PATCH v4 net-next 00/19] inet: frags: bring rhashtables to IP defrag Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 01/19] ipv6: frag: remove unused field Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 02/19] inet: frags: change inet_frags_init_net() return value Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 03/19] inet: frags: add a pointer to struct netns_frags Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 04/19] inet: frags: refactor ipv6_frag_init() Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 05/19] inet: frags: refactor lowpan_net_frag_init() Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 06/19] inet: frags: refactor ipfrag_init() Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 07/19] rhashtable: add schedule points Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 08/19] inet: frags: use rhashtables for reassembly units Eric Dumazet
2018-04-16 12:54 ` Stefan Schmidt
2018-03-31 19:58 ` [PATCH v4 net-next 09/19] inet: frags: remove some helpers Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 10/19] inet: frags: get rif of inet_frag_evicting() Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 11/19] inet: frags: remove inet_frag_maybe_warn_overflow() Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 12/19] inet: frags: break the 2GB limit for frags storage Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 13/19] inet: frags: do not clone skb in ip_expire() Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 14/19] ipv6: frags: rewrite ip6_expire_frag_queue() Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 15/19] rhashtable: reorganize struct rhashtable layout Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 16/19] inet: frags: reorganize struct netns_frags Eric Dumazet
2018-03-31 19:58 ` [PATCH v4 net-next 17/19] inet: frags: get rid of ipfrag_skb_cb/FRAG_CB Eric Dumazet
2018-04-01 3:02 ` kbuild test robot
2018-03-31 19:58 ` [PATCH v4 net-next 18/19] ipv6: frags: get rid of ip6frag_skb_cb/FRAG6_CB Eric Dumazet
2018-03-31 19:59 ` [PATCH v4 net-next 19/19] inet: frags: get rid of nf_ct_frag6_skb_cb/NFCT_FRAG6_CB Eric Dumazet
2018-04-01 3:25 ` [PATCH v4 net-next 00/19] inet: frags: bring rhashtables to IP defrag David Miller
2018-05-28 9:12 ` Tariq Toukan
2018-05-28 14:52 ` Alexander Aring
2018-05-28 16:09 ` Eric Dumazet
2018-05-30 7:20 ` Tariq Toukan
2018-05-30 7:36 ` Eric Dumazet
2018-05-30 14:42 ` Tariq Toukan
2018-05-31 12:18 ` Moshe Shemesh
2018-05-31 14:05 ` Eric Dumazet
2018-05-30 9:20 ` Jesper Dangaard Brouer [this message]
2018-05-30 10:36 ` Eric Dumazet
2018-05-30 10:56 ` Eric Dumazet
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=20180530112022.2b793051@redhat.com \
--to=brouer@redhat.com \
--cc=alex.aring@gmail.com \
--cc=aring@mojatatu.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eranbe@mellanox.com \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=ktkhai@virtuozzo.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hpe.com \
--cc=stefan@osg.samsung.com \
--cc=tariqt@mellanox.com \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).