DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re:  [PATCH] test: add reassembly perf test
Date: Fri, 3 Apr 2020 16:59:07 +0000	[thread overview]
Message-ID: <CY4PR1801MB18630BCE47819AAA4D534532DEC70@CY4PR1801MB1863.namprd18.prod.outlook.com> (raw)
In-Reply-To: <f7t4ku0d03l.fsf@dhcp-25.97.bos.redhat.com>

>> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>
>> Add reassembly perf autotest for both ipv4 and ipv6 reassembly.
>> Each test is performed with vairable number of fragments per flow,
>> either ordered or unorderd fragments and interleaved flows.
>>
>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>> ---
>>  app/test/meson.build            |   2 +
>>  app/test/test_reassembly_perf.c | 989
>++++++++++++++++++++++++++++++++
>>  2 files changed, 991 insertions(+)
>>  create mode 100644 app/test/test_reassembly_perf.c
>>

<snip>

>> +		pkt_len = frag_len;
>> +		/*
>> +		 * Initialize UDP header.
>> +		 */
>> +		if (i == 0) {
>> +			udp_hdr->src_port =
>rte_cpu_to_be_16(UDP_SRC_PORT);
>> +			udp_hdr->dst_port =
>rte_cpu_to_be_16(UDP_DST_PORT);
>> +			udp_hdr->dgram_len =
>rte_cpu_to_be_16(pkt_len);
>> +			udp_hdr->dgram_cksum = 0; /* No UDP
>checksum. */
>
>                        ^^^ This is expressly forbidden in ipv6 (see
>                            RFC2460).  Is the fragment reassembly not
>                            caring about this?  I didn't check if ipv6
>                            fragmenting code actually generates a proper
>                            udp checksum, either.

Nope reassembly doesn't care about L4 header.
I just checked the v6 fragmentation code and it doesn't compute udp checksum.

>
>                            I don't think it should prevent us from
>                            adding this test case, but we should try to
>                            fix it in the library if it isn't already.
>
>> +		}
>> +
>> +		/*
>> +		 * Initialize IP header.
>> +		 */
>> +		pkt_len = (uint16_t)(pkt_len + sizeof(struct
>rte_ipv6_hdr) +
>> +				     RTE_IPV6_FRAG_HDR_SIZE);
>> +		ip_hdr->vtc_flow = rte_cpu_to_be_32(IP6_VERSION <<


      reply	other threads:[~2020-04-03 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 11:50 [dpdk-dev] " pbhagavatula
2020-04-03 16:07 ` Aaron Conole
2020-04-03 16:59   ` Pavan Nikhilesh Bhagavatula [this message]

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=CY4PR1801MB18630BCE47819AAA4D534532DEC70@CY4PR1801MB1863.namprd18.prod.outlook.com \
    --to=pbhagavatula@marvell.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.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;
as well as URLs for NNTP newsgroup(s).