Re: [dpdk-dev] [PATCH v3] ip_frag: recalculate data length of fragment

2020-12-12 Thread luyicai
Hi, Thank you so much for your review! I absolutely agree with that, and I'll resubmit a patch as soon as possible. > -Original Message- > From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com] > Sent: Monday, December 7, 2020 8:25 PM > To: luyicai ; dev@dpdk.org > Cc: Zhoujingbi

Re: [dpdk-dev] [PATCH v3] ip_frag: recalculate data length of fragment

2020-12-07 Thread Ananyev, Konstantin
Hi, > In some situations, we would get several ip fragments, which total > data length is less than minimum frame(64) and padding with zeros. > Examples: Second Fragment "a0a1 a2a3 a4a5 a6a7 ..." > and Third Fragment "a8a9 aaab acad aeaf b0b1 b2b3 ...". > Finally, we would reassemble

Re: [dpdk-dev] [PATCH v3] ip_frag: recalculate data length of fragment

2020-12-03 Thread Aaron Conole
Yicai Lu writes: > In some situations, we would get several ip fragments, which total > data length is less than minimum frame(64) and padding with zeros. > Examples: Second Fragment "a0a1 a2a3 a4a5 a6a7 ..." > and Third Fragment "a8a9 aaab acad aeaf b0b1 b2b3 ...". > Finally, we would

[dpdk-dev] [PATCH v3] ip_frag: recalculate data length of fragment

2020-12-03 Thread Yicai Lu
In some situations, we would get several ip fragments, which total data length is less than minimum frame(64) and padding with zeros. Examples: Second Fragment "a0a1 a2a3 a4a5 a6a7 ..." and Third Fragment "a8a9 aaab acad aeaf b0b1 b2b3 ...". Finally, we would reassemble Second and Third F