From: "Liu, Yong" <yong.liu@intel.com>
To: "Qiu, Michael" <michael.qiu@intel.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [patch] ironpond , twinpond and springfountain 's mbuf is 2048, not 1024
Date: Tue, 20 Oct 2015 03:19:04 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10F2E005@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <234E41FA-C8E6-470A-95DD-5253859F9B35@intel.com>
I'm not sure why use 2048 for some NICs. Anybody known about this?
Scatter feature is used when received packets over the size of mbuf.
I think 1024 and 2048 should be the same to measure this feature.
> -----Original Message-----
> From: Qiu, Michael
> Sent: Tuesday, October 20, 2015 11:05 AM
> To: Liu, Yong
> Cc: Tu, LijuanX A; dts@dpdk.org
> Subject: Re: [dts] [patch] ironpond , twinpond and springfountain 's mbuf
> is 2048, not 1024
>
> I have a question, which nic's default mbuf is 1024?
> Thanks,
> Michael
>
> 发自我的 iPhone
>
> > 在 2015年10月20日,上午10:23,Liu, Yong <yong.liu@intel.com> 写道:
> >
> > Applied. Thx.
> >
> >> -----Original Message-----
> >> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lijuan tu
> >> Sent: Thursday, October 15, 2015 12:25 PM
> >> To: dts@dpdk.org
> >> Subject: [dts] [patch] ironpond , twinpond and springfountain 's mbuf
> is
> >> 2048, not 1024
> >>
> >> Signed-off-by: lijuan tu <lijuanx.a.tu@intel.com>
> >> ---
> >> tests/TestSuite_scatter.py | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/tests/TestSuite_scatter.py b/tests/TestSuite_scatter.py
> >> index abb1a08..1bec2c8 100644
> >> --- a/tests/TestSuite_scatter.py
> >> +++ b/tests/TestSuite_scatter.py
> >> @@ -55,7 +55,7 @@ class TestScatter(TestCase):
> >> # Verify that enough ports are available
> >> self.verify(len(dutPorts) >= 2, "Insufficient ports")
> >> self.pmdout = PmdOutput(self.dut)
> >> - if self.nic in ["niantic", "fortville_eagle",
> "fortville_spirit",
> >> "fortville_spirit_single", "redrockcanyou"]:
> >> + if self.nic in ["niantic", "fortville_eagle",
> "fortville_spirit",
> >> "fortville_spirit_single", "redrockcanyou", "ironpond", "twinpond",
> >> "springfountain"]:
> >> self.mbsize = 2048
> >> else:
> >> self.mbsize = 1024
> >> --
> >> 2.1.0
> >
next prev parent reply other threads:[~2015-10-20 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 4:24 lijuan tu
2015-10-20 2:22 ` Liu, Yong
2015-10-20 3:04 ` Qiu, Michael
2015-10-20 3:19 ` Liu, Yong [this message]
2015-10-20 4:45 ` Tu, LijuanX A
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=86228AFD5BCD8E4EBFD2B90117B5E81E10F2E005@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=michael.qiu@intel.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).