From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Fu, JingguoX" <jingguox.fu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] virtio: Support mergeable buffer in virtio pmd
Date: Wed, 24 Sep 2014 11:31:46 +0200 [thread overview]
Message-ID: <2446963.gpRyEul7fH@xps13> (raw)
In-Reply-To: <6BD6202160B55B409D423293115822625483B6@SHSMSX101.ccr.corp.intel.com>
Hi Jingguo,
2014-09-24 09:22, Fu, JingguoX:
> Tested-by: Jingguo Fu <jingguox.fu at intel.com>
>
> This patch includes 1 files, and has been tested by Intel.
> Please see information as the following:
>
> Host:
> Fedora 19 x86_64, Linux Kernel 3.9.0, GCC 4.8.2 Intel Xeon CPU E5-2680 v2 @ 2.80GHz
> NIC: Intel Niantic 82599, Intel i350, Intel 82580 and Intel 82576
>
> Guest:
> Fedora 16 x86_64, Linux Kernel 3.4.2, GCC 4.6.3 Qemu emulator 1.4.2
>
> This patch tests with user space vhost driver library patch.
> We verified zero copy and one copy test cases for functional and performance.
>
> This patch depend on the two patches:
> [dpdk-dev] [PATCH] virtio: Update max RX packet length http://www.dpdk.org/ml/archives/dev/2014-September/005107.html
> [dpdk-dev] [PATCH] virtio: Fix vring entry number issue http://www.dpdk.org/ml/archives/dev/2014-September/005170.html
This patch and the previous one (Support jumbo frame in user space vhost)
were part of release 1.7.1.
You already sent an email about this test:
http://dpdk.org/ml/archives/dev/2014-July/004466.html
So I'm not sure it deserves another email today.
--
Thomas
next prev parent reply other threads:[~2014-09-24 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 8:54 Ouyang Changchun
2014-08-21 1:23 ` Ouyang, Changchun
2014-08-25 15:16 ` Thomas Monjalon
2014-09-24 9:22 ` Fu, JingguoX
2014-09-24 9:31 ` Thomas Monjalon [this message]
2014-09-24 14:26 ` Ouyang, Changchun
2014-09-25 0:47 ` Fu, JingguoX
2014-09-25 7:12 ` Thomas Monjalon
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=2446963.gpRyEul7fH@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jingguox.fu@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).