From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ouyang Changchun <changchun.ouyang@intel.com>
Cc: dev@dpdk.org, min.cao@intel.com
Subject: Re: [dpdk-dev] [PATCH v4 0/2] Support multiple queues feature in DPDK based virtio-net frontend
Date: Thu, 29 May 2014 11:23:31 +0200 [thread overview]
Message-ID: <2851736.NovQdoEyUE@xps13> (raw)
In-Reply-To: <1401347900-25587-1-git-send-email-changchun.ouyang@intel.com>
2014-05-29 15:18, Ouyang Changchun:
> This v4 patch series replace previous v1, v2, v3 patch for virtio-net
> multiple queues feature. Please apply this v4 patch series and ignore
> previous patches.
>
> It splits previous one patch into the following 2 patches for easy to
> review: Cleanup the existing codes in virtio-net PMD;
> Support multiple queues feature in DPDK based virtio-net frontend;
>
> In sum, this patch supports multiple queues feature in DPDK based virtio-net
> frontend. It firstly gets max queue number of virtio-net from virtio PCI
> configuration and then send command to negotiate the queue number with
> backend; When receiving and transmitting packets, it negotiates multiple
> virtio-net queues which serve RX/TX; To utilize this feature, the backend
> also need support multiple queues feature and enable it.
>
> Ouyang Changchun (2):
> Cleanup the existing codes in virtio-net PMD.
> Support multiple queues feature in DPDK based virtio-net frontend.
Doing clean-up and splitting it in a separated patch is really nice.
Thank you for your rework.
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied for version 1.7.0.
Thanks
--
Thomas
prev parent reply other threads:[~2014-05-29 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 7:18 Ouyang Changchun
2014-05-29 7:18 ` [dpdk-dev] [PATCH v4 1/2] virtio: Cleanup the existing codes in virtio-net PMD Ouyang Changchun
2014-05-29 7:18 ` [dpdk-dev] [PATCH v4 2/2] virtio: Support multiple queues feature in DPDK based virtio-net frontend Ouyang Changchun
2014-05-29 9:23 ` 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=2851736.NovQdoEyUE@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=min.cao@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).