DPDK patches and discussions
 help / color / mirror / Atom feed
From: sothy shan <sothy.e98@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_dev_configure
Date: Thu, 24 Jul 2014 15:00:45 +0200	[thread overview]
Message-ID: <CAHcF_0a_UkiQmzKtuWCDLviVLdLjuAAggHnoYHt8vAc+rCMrqQ@mail.gmail.com> (raw)
In-Reply-To: <4680006.49a2zB1OLs@xps13>

I have problem when I try dpdk ovs with DPDK 1.7. DPDK 1.7 alone working
well.

Drive I installed is compiled with T=x86_64-ivshmem-linuxapp-gcc.

I am not sure when I using DPDK ovs, how to debug at DPDK 1.7.0 code. I
guess I need to enable to print PMD_DEBUG_TRACE message. At this point,
DPDK ovs message is only printed.

I too suspect it is problem with port_conf message. Not sure. First I need
to know how to use PMD_DEBUG_TRACE with DPDK_ovs.

You understand my question?

Thanks again



On Thu, Jul 24, 2014 at 2:51 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:

> 2014-07-24 14:44, Thomas Monjalon:
> > 2014-07-24 14:34, sothy shan:
> > > Second, any clue why rte_eth_dev_configure give an error with code -22?
> >
> > It depends of your driver.
> > Example: #define IXGBE_ERR_NO_SAN_ADDR_PTR -22
>
> It's more probably -EINVAL without driver dependency.
> It means there is a mistake in your configuration.
> PMD_DEBUG_TRACE will help you.
>
> --
> Thomas
>

  reply	other threads:[~2014-07-24 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 12:34 sothy shan
2014-07-24 12:44 ` Thomas Monjalon
2014-07-24 12:51   ` Thomas Monjalon
2014-07-24 13:00     ` sothy shan [this message]
2014-07-24 13:05       ` Thomas Monjalon
2014-07-24 14:15         ` sothy shan

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=CAHcF_0a_UkiQmzKtuWCDLviVLdLjuAAggHnoYHt8vAc+rCMrqQ@mail.gmail.com \
    --to=sothy.e98@gmail.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).