From: "Liu, Yong" <yong.liu@intel.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] test_plan/dynamic_queue: add dynamic queue test plan
Date: Mon, 20 Aug 2018 06:38:59 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E63129AA1@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <0D300480287911409D9FF92C1FA2A3355B3D81E7@SHSMSX104.ccr.corp.intel.com>
Thanks for clear it, xueqin. Please also add this information in test plan.
> -----Original Message-----
> From: Lin, Xueqin
> Sent: Monday, August 20, 2018 1:07 PM
> To: Liu, Yong <yong.liu@intel.com>; dts@dpdk.org
> Subject: RE: [dts] [PATCH] test_plan/dynamic_queue: add dynamic queue test
> plan
>
> Yes, queue stop is must, if not stop queue, will fail to setup this queue
> next.
> Use cmd to start testpmd, application first specifies how many Tx and Rx
> queues to include in the ethdev, such as "--txq=4 --rxq=4",
> the application then sets up each 4 Tx and 4 Rx queues. Finally, once all the
> queues have been set up, the application may then start the device,
> then traffic can flow. If device stops, this halts the flow of traffic on all
> queues in the ethdev, not stop one queue.
> So device stop is different from queue stop.
>
> Best regards,
> Xueqin
>
> > -----Original Message-----
> > From: Liu, Yong
> > Sent: Monday, August 20, 2018 5:24 PM
> > To: Lin, Xueqin <xueqin.lin@intel.com>; dts@dpdk.org
> > Subject: Re: [dts] [PATCH] test_plan/dynamic_queue: add dynamic queue
> > test plan
> >
> >
> >
> > On 08/07/2018 12:23 PM, Xueqin Lin wrote:
> > > +Test Case: Rx queue configure at runtime
> > > +========================================
> > > +Stop some Rx queues on port 0::
> > > +
> > > + testpmd> port 0 rxq <id> stop
> > > +
> > > +Set rxonly forward, start testpmd
> > > +
> > > +Send different src or dst IPv4 packets::
> > > +
> > > + p=Ether()/IP(src="192.168.0.1", dst="192.168.0.1")/Raw("x"*20)
> > > +
> > > +Stop testpmd, find stopped queues can't receive packets, but other
> > > +queues could receive packets
> > Hi Xueqin,
> > In the introduction chapter of this test plan, you have mentioned that no
> > need to call dev_stop when configuring queue.
> > Is here queue stop is must? If it is yes, please add some note for
> difference
> > between device stop and queue stop.
> >
> > Thanks,
> > Marvin
next prev parent reply other threads:[~2018-08-20 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 4:23 Xueqin Lin
2018-08-20 9:23 ` Liu, Yong
2018-08-20 5:07 ` Lin, Xueqin
2018-08-20 6:38 ` Liu, Yong [this message]
2018-08-20 6:41 ` Lin, Xueqin
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=86228AFD5BCD8E4EBFD2B90117B5E81E63129AA1@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=xueqin.lin@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).