From: Lazaros Koromilas <l@nofutznetworks.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Attaching to an ethernet port from a secondary process
Date: Fri, 19 Feb 2016 18:22:00 +0200 [thread overview]
Message-ID: <CAHPNE8hWhKGnnKTfQmzn5mvJ=SDSDwarOu5nzOZbx=S8JDyOQw@mail.gmail.com> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831FFC5723@IRSMSX109.ger.corp.intel.com>
Thanks for your reply Reshma, that clears things up.
Lazaros.
On Fri, Feb 19, 2016 at 2:58 PM, Pattan, Reshma <reshma.pattan@intel.com> wrote:
> Hi,
>
>> -----Original Message-----
>> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Lazaros Koromilas
>> Sent: Wednesday, February 17, 2016 11:40 AM
>> To: users@dpdk.org
>> Subject: Re: [dpdk-users] Attaching to an ethernet port from a secondary
>> process
>>
>> On Wed, Feb 17, 2016 at 1:17 PM, Lazaros Koromilas <l@nofutznetworks.com>
>> wrote:
>> > Hi all,
>> >
>> > I'm trying to take advantage of the multi-process support together
>> > with the port hotplugging framework. The idea is that my primary
>> > process will configure all ports I'm going to need and then secondary
>> > processes will come up, selectively attach to ports and perform rx/tx.
>
> From quick glance of dpdk code what I see is rte_eth_dev_attach will not attach existing port to DPDK app.
> Because from "librte_ether/rte_ethdev.c" rte_eth_dev_attach()==> rte_eth_dev_attach_vdev()==>rte_eal_vdev_init() creates new vdev and returns you the port id.
> And moreover vdevs are local to process.
> You may have to check clearly what is the hot plug functionality and do you really need it in your case.
>
>> > Where pcap{0,1}-in.pcap files are pcap dumps. The primary will
>> > initialize the ports and pause(2). The secondary will attach to the
>> > same ports and do work. The latter then segfaults in
>> > rte_eth_rx_burst() with dev->data->{rx,tx}_queues being NULL pointers.
>> >
>
> Since in secondary new device is created, but device configuration and queue configuration is not done, crash is expected.
>
> Thanks,
> Reshma
prev parent reply other threads:[~2016-02-19 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 11:17 Lazaros Koromilas
2016-02-17 11:40 ` Lazaros Koromilas
2016-02-19 12:58 ` Pattan, Reshma
2016-02-19 16:22 ` Lazaros Koromilas [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='CAHPNE8hWhKGnnKTfQmzn5mvJ=SDSDwarOu5nzOZbx=S8JDyOQw@mail.gmail.com' \
--to=l@nofutznetworks.com \
--cc=reshma.pattan@intel.com \
--cc=users@dpdk.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).