From: Sam <batmanustc@gmail.com>
To: dev@dpdk.org, ovs-dev@openvswitch.org
Subject: Re: [dpdk-dev] In ovs-2.4 version, why can't stop dpdk-bond port by `ovs-ofctl mod br dpdkbond DOWN`?
Date: Mon, 27 Nov 2017 18:08:21 +0800 [thread overview]
Message-ID: <CAOE=1Z1y=eS2s9vkou29qNBdajQywAqnjK9_vRE_Zdj6jETxUg@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z3bo+iDps96mWNfVmOVEZg51sR3Mf5tMp7WdV8_k0dO8w@mail.gmail.com>
The "dev->port_id" is bond port id, should I use slave port id instead ?
2017-11-27 18:07 GMT+08:00 Sam <batmanustc@gmail.com>:
> Hi all,
>
> I'm working in ovs 2.4 version, and I use "dpdkb" type netdev. Then I
> call `ovs-ofctl mod br dpdkbond DOWN` to down this device, at last, my
> code call "rte_eth_dev_stop(dev->port_id);".
>
> But counter shows the port is still rx/tx, why?
>
next prev parent reply other threads:[~2017-11-27 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 10:07 Sam
2017-11-27 10:08 ` Sam [this message]
2017-11-27 19:28 ` [dpdk-dev] [ovs-dev] " Ben Pfaff
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='CAOE=1Z1y=eS2s9vkou29qNBdajQywAqnjK9_vRE_Zdj6jETxUg@mail.gmail.com' \
--to=batmanustc@gmail.com \
--cc=dev@dpdk.org \
--cc=ovs-dev@openvswitch.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).