Re:Re: [PATCH v5] ip_frag: add IPv4 options fragment and test data

Hi everyone, I have resubmitted the patch.Thanks. https://patchwork.dpdk.org/project/dpdk/patch/1649649325-1942-1-git-send-email-chcch...@163.com/ Huichao,Cai

Re: [PATCH v5] ip_frag: add IPv4 options fragment and test data

n of test harness. > > Aaron, is there any better way to deal with it? At the moment, no. We do have an effort for resubmits to be requested - but that hasn't been completed yet. > Thanks > > Konstantin > > > > > > From: Huichao Cai > Sent: Wed

RE: Re:RE: [PATCH v5] ip_frag: add IPv4 options fragment and test data

the patch to force another run of test harness. Aaron, is there any better way to deal with it? Thanks Konstantin From: Huichao Cai Sent: Wednesday, April 6, 2022 2:22 AM To: Ananyev, Konstantin Cc: dev@dpdk.org Subject: Re:RE: [PATCH v5] ip_frag: add IPv4 options fragment and test data Hi

Re:RE: [PATCH v5] ip_frag: add IPv4 options fragment and test data

Hi Konstantin, This patch has a test case failure:ci/iol-broadcom-Functional. Failed Tests: - mtu_update - scatter The same goes for many other patches,Do I need to deal with it, how to deal with it? Huichao,Cai

RE: [PATCH v5] ip_frag: add IPv4 options fragment and test data

> According to RFC791,the options may appear or not in datagrams. > They must be implemented by all IP modules (host and gateways). > What is optional is their transmission in any particular datagram, > not their implementation.So we have to deal with it during the > fragmenting process.Add some

[PATCH v5] ip_frag: add IPv4 options fragment and test data

According to RFC791,the options may appear or not in datagrams. They must be implemented by all IP modules (host and gateways). What is optional is their transmission in any particular datagram, not their implementation.So we have to deal with it during the fragmenting process.Add some test data fo