DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yong Wang <wang.yong19@zte.com.cn>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org, Yong Wang <wang.yong19@zte.com.cn>
Subject: [dpdk-dev] [PATCH] doc: fix typos in virtio howto guide
Date: Mon, 19 Jun 2017 06:14:23 -0400	[thread overview]
Message-ID: <1497867263-25525-1-git-send-email-wang.yong19@zte.com.cn> (raw)

Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
---
 doc/guides/howto/virtio_user_as_exceptional_path.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/howto/virtio_user_as_exceptional_path.rst b/doc/guides/howto/virtio_user_as_exceptional_path.rst
index 0bbcd3f..3f99fe8 100644
--- a/doc/guides/howto/virtio_user_as_exceptional_path.rst
+++ b/doc/guides/howto/virtio_user_as_exceptional_path.rst
@@ -54,7 +54,7 @@ solution is very promising in:
 *   Performance
 
     similar to KNI, this solution would use one or more kthreads to
-    send/receive packets from user space DPDK applications, which has little
+    send/receive packets to/from user space DPDK applications, which has little
     impact on user space polling thread (except that it might enter into kernel
     space to wake up those kthreads if necessary).
 
@@ -94,7 +94,7 @@ compiling the kernel and those kernel modules should be inserted.
 
     This is used to negotiate VIRTIO_NET_F_GUEST_TSO4 and
     VIRTIO_NET_F_GUEST_TSO6 feature so that large packets from kernel can be
-    transmitted DPDK application and further TSOed by physical NIC.
+    transmitted to DPDK application and further TSOed by physical NIC.
 
 * ``--enable-rx-cksum``
 
-- 
1.8.3.1

             reply	other threads:[~2017-06-19 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 10:14 Yong Wang [this message]
2017-06-26 14:59 ` Mcnamara, John
2017-07-02 17:37   ` 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=1497867263-25525-1-git-send-email-wang.yong19@zte.com.cn \
    --to=wang.yong19@zte.com.cn \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).