From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "Dey, Souvik" <sodey@sonusnet.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] tx_burst errors seen with virtual pmds
Date: Thu, 7 Jan 2016 08:48:05 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E36031D134B@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <BN3PR0301MB12020734A9756398B23071D7DAF50@BN3PR0301MB1202.namprd03.prod.outlook.com>
Hi Souvik,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Dey, Souvik
> Sent: Thursday, January 7, 2016 2:15 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] tx_burst errors seen with virtual pmds
>
> Hi All,
> While trying call load with virtio_pmd/vmxnet3_pmd , I am seeing
> that at around 100Mbps, we are having tx_burst errors. We are currently
> using DPDK 2.1 and send 1 packet at a time. When we try the same with
> ixgbe_vf we are not seeing similar drops. Is there any issues with the virtual
> pmds which is causing this tx drops. We are using tx descriptor as 1024 and 1
> tx queue to send out packets.
>
> --
> Regards,
> Souvik
IMO, for virtio and vmxnet3, there's a frontend in guest and a backend in host.
And mostly, backend driver does the data copies, which spends more CPU than
frontend. So the tx descriptor queue could be always full, which leads to tx error.
Thanks,
Jianfeng
next prev parent reply other threads:[~2016-01-07 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 6:15 Dey, Souvik
2016-01-07 8:48 ` Tan, Jianfeng [this message]
2016-01-07 9:40 ` Dey, Souvik
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=ED26CBA2FAD1BF48A8719AEF02201E36031D134B@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=sodey@sonusnet.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).