DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gregory Etelson <gregory@weka.io>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] ixgbevf: queue start stop functions
Date: Tue, 23 May 2017 14:12:49 +0300	[thread overview]
Message-ID: <2686885.NDBBRvgq08@polaris> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B5BB9B3@shsmsx102.ccr.corp.intel.com>

Hello,

I'm working on a procedure that will handle Ethernet link failure over ixgbe VF.
Without queues reset functionality I tried to reset DPDK port with 
rte_eth_dev_stop();rte_eth_dev_start() sequence.
My tests show that call to dev_stop can hang a process.
Can you suggest another procedure for VF port reset on link down ?

Thank you.

Regards,
Gregory  


On Tuesday, 23 May 2017 03:53:06 IDT Lu, Wenzhuo wrote:
> Hi Gregory,
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gregory Etelson
> > Sent: Monday, May 22, 2017 5:36 PM
> > To: dev@dpdk.org
> > Cc: Richardson, Bruce; Yigit, Ferruh; Zhang, Qi Z
> > Subject: [dpdk-dev] ixgbevf: queue start stop functions
> > 
> > Hello,
> > 
> > ixgbevf PMD has no implementation for RX/TX queue start/stop functions in
> > DPDK-17.05.0 Is there a roadmap to add these functions to DPDK ?
> I'm afraid there's no plan to support it because lack of interface between PF and VF :(
> 
> > 
> > Thank you
> > Regards,
> > Gregory

  reply	other threads:[~2017-05-23 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22  9:35 Gregory Etelson
2017-05-23  0:53 ` Lu, Wenzhuo
2017-05-23 11:12   ` Gregory Etelson [this message]
2017-05-24  1:33     ` Lu, Wenzhuo

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=2686885.NDBBRvgq08@polaris \
    --to=gregory@weka.io \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=wenzhuo.lu@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).