From: James Yu <ypyu2011@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Any benefit of using DPDK's makefiles instead of using
Date: Fri, 17 Jan 2014 00:43:13 -0800 [thread overview]
Message-ID: <CAFMB=kBGrh+-3P-y8-sYE7ZXZW1oUYbcdgos34t7oYt_3_rURA@mail.gmail.com> (raw)
In-Reply-To: <CAFMB=kCaeOi3nz9orC+X9ZnFOMq7DcGG02d38-HD=tWhyer1Jg@mail.gmail.com>
Please ignore this post. I re-post it with the right subject. Sorry about
this.
On Fri, Jan 17, 2014 at 12:40 AM, James Yu <ypyu2011@gmail.com> wrote:
> Anyone knows how to turn off TSO in DPDK+SR-IOV in KVM guest VM ? I want
> the packets sending out of the KVM host not to have TSO by the hardware.
>
> I imagine that I need to do the following:
> 1. turn off TSO in the guest before starting DPDK using ethtool -K ethX
> tso off
> After DPDK is started, the device will be removed.
> I think the command ethtool will call ethtool function in the
> ixgbevf.ko in the kernel to turn TSO off. Am I correct ?
> 2. turn off TSO on the host using ethtool -K ethX tso off
>
> Do I need to do the second one ? Would the first one propagate down to the
> host ?
>
> James
>
prev parent reply other threads:[~2014-01-17 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 8:40 James Yu
2014-01-17 8:43 ` James Yu [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='CAFMB=kBGrh+-3P-y8-sYE7ZXZW1oUYbcdgos34t7oYt_3_rURA@mail.gmail.com' \
--to=ypyu2011@gmail.com \
--cc=dev@dpdk.org \
/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).