DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_tx_queue_setup() failing (error -22) when setting up tx queues on a VMXNET3 port...
Date: Wed, 25 Nov 2015 18:59:03 +0100	[thread overview]
Message-ID: <2079132.PHeD38B2Uf@xps13> (raw)
In-Reply-To: <23c134dd50bf4f9ead41dc6b3467984f@bilemail1.empirix.com>

2015-11-25 17:55, Montorsi, Francesco:
> Since I was using the rte_eth_rx_queue_count() function in one place, and VMXNET3 does not support it, I'm getting a SEGFAULT.
> So next question is:  is user's task to check for validity of pointers inside dev_ops before calling driver functions? Because rte_eth_rx_queue_count() and companion funcitons have no safety checks apparently (!!!)

Bruce already sent a fix for this issue.
It should be applied on HEAD in few minutes.

      reply	other threads:[~2015-11-25 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 10:32 Montorsi, Francesco
2015-11-25 16:07 ` Stephen Hemminger
2015-11-25 17:55   ` Montorsi, Francesco
2015-11-25 17:59     ` Thomas Monjalon [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=2079132.PHeD38B2Uf@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=fmontorsi@empirix.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).