From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yong Liu <yong.liu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/qos_sched: fix flow pause after 2M packets
Date: Thu, 03 Jul 2014 16:43:43 +0200 [thread overview]
Message-ID: <18247970.t4289tJKVc@xps13> (raw)
In-Reply-To: <1404377976-9231-1-git-send-email-yong.liu@intel.com>
2014-07-03 16:59, Yong Liu:
> After enable vector pmd, qos_sched only send 32 packets every burst.
> That will cause some packets not transmitted and therefore mempool
> will be drain after a while.
> App qos_sched now will re-send the packets which failed to send out in
> previous tx function.
>
> Signed-off-by: Yong Liu <yong.liu@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> Tested-by: Waterman Cao <waterman.cao@intel.com>
Applied for version 1.7.0 as it was a blocker for vectorized ixgbe + QoS.
--
Thomas
prev parent reply other threads:[~2014-07-03 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 8:59 Yong Liu
2014-07-03 10:07 ` Xie, Huawei
2014-07-03 10:54 ` Dumitrescu, Cristian
2014-07-03 10:55 ` Dumitrescu, Cristian
2014-07-03 14:43 ` Thomas Monjalon [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=18247970.t4289tJKVc@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=yong.liu@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).