DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"bugzilla@dpdk.org" <bugzilla@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [Bug 320] mlx4: info get fails in secondary process
Date: Fri, 19 Jul 2019 05:55:20 +0000	[thread overview]
Message-ID: <VI1PR05MB3278ED8D4F72CC4F15CF5DDAD2CB0@VI1PR05MB3278.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20190712140358.6761361a@hermes.lan>

Is it really needed for mlx4? mlx4 uses neither Netlink nor shared context.

With best regards, Slava

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Stephen Hemminger
> Sent: Saturday, July 13, 2019 0:04
> To: bugzilla@dpdk.org
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [Bug 320] mlx4: info get fails in secondary process
> 
> On Fri, 12 Jul 2019 20:04:26 +0000
> bugzilla@dpdk.org wrote:
> 
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> >
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D320&amp;data=02%7C01%7Cviachesla
> vo%40m
> >
> ellanox.com%7Cc75dc339868c42296e5c08d7070c7dbf%7Ca652971c7d2e4d
> 9ba6a4d
> >
> 149256f461b%7C0%7C0%7C636985622553681551&amp;sdata=hyzFADnV52
> GNWXbCPFK
> > zmUZS6j6gPbzNAxIqLrM%2BLRM%3D&amp;reserved=0
> >
> >             Bug ID: 320
> >            Summary: mlx4: info get fails in secondary process
> >            Product: DPDK
> >            Version: 19.08
> >           Hardware: All
> >                 OS: All
> >             Status: UNCONFIRMED
> >           Severity: normal
> >           Priority: Normal
> >          Component: other
> >           Assignee: dev@dpdk.org
> >           Reporter: stephen@networkplumber.org
> >   Target Milestone: ---
> >
> > Attempts to do dev_info_get in secondary process fail because the
> > driver handle to infiniband (priv->ctx) is not valid in secondary process. This
> leads to:
> >
> > #0  0x00007ffff5d06ab4 in _IO_vfprintf_internal
> > (s=s@entry=0x7fffffffe3c0, format=<optimized out>,
> > format@entry=0x7ffff496a605 "%s/device/net",
> > ap=ap@entry=0x7fffffffe528) at vfprintf.c:1635
> > #1  0x00007ffff5d32599 in _IO_vsnprintf (string=0x7fffffffe4b0 "",
> > maxlen=<optimized out>, format=0x7ffff496a605 "%s/device/net",
> > args=args@entry=0x7fffffffe528) at vsnprintf.c:119
> > #2  0x00007ffff5d0fd32 in __snprintf (s=s@entry=0x0,
> > maxlen=maxlen@entry=0,
> > format=format@entry=0x7ffff496a605 "%s/device/net") at snprintf.c:34
> > #3  0x00007ffff4720b8b in mlx4_get_ifname
> > (priv=priv@entry=0xc0137e93c0,
> > ifname=ifname@entry=0x7fffffffe690) at
> > /usr/src/redhat/BUILD/dpdk-18.11/drivers/net/mlx4/mlx4_ethdev.c:71
> > #4  0x00007ffff47214e4 in mlx4_dev_infos_get (dev=<optimized out>,
> > info=0x7fffffffe6e0) at
> > /usr/src/redhat/BUILD/dpdk-18.11/drivers/net/mlx4/mlx4_ethdev.c:583
> > #5  0x00007ffff44b896c in rte_eth_dev_info_get
> > (port_id=port_id@entry=0,
> > dev_info=dev_info@entry=0x7fffffffe6e0) at
> > /usr/src/redhat/BUILD/dpdk-18.11/lib/librte_ethdev/rte_ethdev.c:2532
> >
> 
> I am testing a patch for this.

      reply	other threads:[~2019-07-19  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 20:04 bugzilla
2019-07-12 21:03 ` Stephen Hemminger
2019-07-19  5:55   ` Slava Ovsiienko [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=VI1PR05MB3278ED8D4F72CC4F15CF5DDAD2CB0@VI1PR05MB3278.eurprd05.prod.outlook.com \
    --to=viacheslavo@mellanox.com \
    --cc=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).