DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olga Shern <olgas@mellanox.com>
To: Bill O'Hara <billtohara@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Multi-process model and mlx4 pmd
Date: Thu, 11 Jun 2015 05:13:17 +0000	[thread overview]
Message-ID: <AM2PR05MB09950359D71595E0931ECB36D3BC0@AM2PR05MB0995.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CABrJh-fAoKettAhCLb8uC+HSdSgf0m8-wRi54OKKyaHJz+mXbg@mail.gmail.com>

Hi Bill, 

Some clarification:

On Mellanox web we have released updated PMD that supports DPDK 1.7/1.8.

the primary and secondary multi-process model limitation is missing  in http://dpdk.org/doc/guides/nics/mlx4.html
just because we  forgot to mention it.

In general,  there is currently no mlx4 PMD that supports this feature, this is current limitation and we plan to add this feature in the future

Best Regards,
Olga


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bill O'Hara
Sent: Wednesday, June 10, 2015 11:33 PM
To: dev@dpdk.org
Subject: [dpdk-dev] Multi-process model and mlx4 pmd

I see from the Mellanox PMD release notes:

http://www.mellanox.com/related-docs/prod_software/Mellanox_ConnectX3_ConnectX3Pro_DPDK_PMD_Release_Notes_v1.7-8_2.8.4.pdf

that the primary and secondary multi-process model is not supported. Though it's not noted as a limitation in the DPDK guide here:

http://dpdk.org/doc/guides/nics/mlx4.html

Can anyone shed light on what the source of the limitation is? Is this something that can be worked around, or fixed in the driver, or something fundamental?

thanks
bill

      reply	other threads:[~2015-06-11  5:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 20:33 Bill O'Hara
2015-06-11  5:13 ` Olga Shern [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=AM2PR05MB09950359D71595E0931ECB36D3BC0@AM2PR05MB0995.eurprd05.prod.outlook.com \
    --to=olgas@mellanox.com \
    --cc=billtohara@gmail.com \
    --cc=dev@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).