From: "Liu, Yong" <yong.liu@intel.com>
To: "Fan, ChangruX" <changrux.fan@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] fix an issue in ipv4_reassembly
Date: Wed, 5 Aug 2015 08:29:00 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10EB55D4@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <84799DAADE9E2A44834F0D0FF8A61A911CC95675@SHSMSX101.ccr.corp.intel.com>
Thanks, Changru. I think it's the root cause of the failure.
From: Fan, ChangruX
Sent: Wednesday, August 05, 2015 4:27 PM
To: Liu, Yong; dts@dpdk.org
Cc: Chen, WeichunX
Subject: fix an issue in ipv4_reassembly
Hi Liu, Yong
The case send_4K_frames_split_in_7_and_4K_maxflows which in ipv4_reassembly is failed on freebsd10.1.
I think the reason is that, in the function set_max_num_of_fragments it's set with an error configuration file.
Please check the patch.
Thank,
changru
prev parent reply other threads:[~2015-08-05 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 8:27 Fan, ChangruX
2015-08-05 8:29 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E10EB55D4@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=changrux.fan@intel.com \
--cc=dts@dpdk.org \
/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).