DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ami Sabo <AmiS@Radware.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/virtio-user: fix multi-process issue
Date: Thu, 23 Feb 2017 09:02:38 +0000	[thread overview]
Message-ID: <25F949B549CFD14EABC392C69312415C0106DBAD3A@ILMB1.corp.radware.com> (raw)
In-Reply-To: <20170223025436.GQ18844@yliu-dev.sh.intel.com>

Mistakenly sent only partial diff. 
Resent the all patch (from the original code base) as a reply to the first message in the thread.

-- Ami

-----Original Message-----
From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com] 
Sent: Thursday, February 23, 2017 4:55 AM
To: Ami Sabo
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] net/virtio-user: fix multi-process issue

On Wed, Feb 22, 2017 at 05:40:28PM +0200, Ami Sabo wrote:
> diff --git a/drivers/net/virtio/virtio_user_ethdev.c 
> b/drivers/net/virtio/virtio_user_ethdev.c
> index 5291294..9b3c266 100644
> --- a/drivers/net/virtio/virtio_user_ethdev.c
> +++ b/drivers/net/virtio/virtio_user_ethdev.c
> @@ -418,25 +418,25 @@ virtio_user_pmd_probe(const char *name, const char *params)
>  		goto end;
>  	}
>  
> -        if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
> -                eth_dev = virtio_user_eth_dev_alloc(name);
> -                if (!eth_dev) {
> -                        PMD_INIT_LOG(ERR, "virtio_user fails to alloc device");
> -                        goto end;
> -                }
> -                hw = eth_dev->data->dev_private;
> -                if (virtio_user_dev_init(hw->virtio_user_dev, path, queues, cq,
> -                                                                 queue_size, mac_addr) < 0) {
> -                        PMD_INIT_LOG(ERR, "virtio_user_dev_init fails");
> -                        virtio_user_eth_dev_free(eth_dev);
> -                        goto end;
> -                }
> -        } else {
> -                eth_dev = rte_eth_dev_attach_secondary(name);
> -                if (!eth_dev) {
> -                        goto end;
> -                }
> -        }

Were you making the patch based on some internal code base? The latest virtio code doesn't have the above code.

> +	if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
> +		eth_dev = virtio_user_eth_dev_alloc(name);
> +		if (!eth_dev) {
> +			PMD_INIT_LOG(ERR, "virtio_user fails to alloc device");
> +			goto end;
> +		}
> +		hw = eth_dev->data->dev_private;
> +		if (virtio_user_dev_init(hw->virtio_user_dev, path, queues, cq,
> +			queue_size, mac_addr) < 0) {
> +		PMD_INIT_LOG(ERR, "virtio_user_dev_init fails");
> +		virtio_user_eth_dev_free(eth_dev);
> +		goto end;
> +		}
> +	} else {
> +		eth_dev = rte_eth_dev_attach_secondary(name);

We also don't have rte_eth_dev_attach_secondary exported, neither.

	--yliu

  reply	other threads:[~2017-02-23  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1487762487-21698-amis@radware.com>
2017-02-22 15:40 ` Ami Sabo
2017-02-23  2:54   ` Yuanhan Liu
2017-02-23  9:02     ` Ami Sabo [this message]
2017-02-23  8:52   ` [dpdk-dev] [PATCH] Signed-off-by: Ami Sabo <amis@radware.com> Ami Sabo

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=25F949B549CFD14EABC392C69312415C0106DBAD3A@ILMB1.corp.radware.com \
    --to=amis@radware.com \
    --cc=dev@dpdk.org \
    --cc=yuanhan.liu@linux.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).