DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 3/3] doc: update mlx guides
Date: Tue, 25 Jul 2017 11:52:39 +0000	[thread overview]
Message-ID: <VI1PR05MB31496495F9E00CB5312F8A55C3B80@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20170725071639.GJ19852@6wind.com>

Adrien,
Thanks for the review. sorry for the caps.
One issue I not agree with below

Tuesday, July 25, 2017 10:17 AM, Adrien Mazarguil:
> Hi Shahaf,
> 
[...]
> >  Currently supported by DPDK:
> >
> > -- Mellanox OFED **4.0-2.0.0.0**.
> > -- Firmware version **2.40.7000**.
> > +- Mellanox OFED **4.1**.
> > +- Firmware version **2.36.5000** and above.
> >  - Supported architectures:  **x86_64** and **POWER8**.
> 
> So x86_64 and POWER8 then? (not "x86" as in "32 bit")
> 
> Actually I'm not sure architecture support can be considered a PMD feature
> given that DPDK itself inevitably supports a larger set. I suggest dropping the
> change made to the "Features" section above.
> 

Actually they are counted as features. See http://dpdk.org/doc/guides/nics/overview.html

  parent reply	other threads:[~2017-07-25 11:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 12:36 [dpdk-dev] [PATCH 1/3] doc: update mlx5 supported features Shahaf Shuler
2017-07-24 12:36 ` [dpdk-dev] [PATCH 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-24 12:36 ` [dpdk-dev] [PATCH 3/3] doc: update mlx guides Shahaf Shuler
     [not found]   ` <20170725071639.GJ19852@6wind.com>
2017-07-25 11:52     ` Shahaf Shuler [this message]
2017-07-25 12:07 ` [dpdk-dev] [PATCH v2 1/3] doc: update mlx5 supported features Shahaf Shuler
2017-07-26  6:48   ` [dpdk-dev] [PATCH v3 " Shahaf Shuler
2017-07-26 17:02     ` [dpdk-dev] [PATCH v4 " Shahaf Shuler
2017-07-28 11:56       ` Mcnamara, John
2017-07-28 14:28       ` [dpdk-dev] [PATCH v5 " Shahaf Shuler
2017-07-28 14:28       ` [dpdk-dev] [PATCH v5 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-28 14:28       ` [dpdk-dev] [PATCH v5 3/3] doc: update mlx guides Shahaf Shuler
2017-07-31 11:26         ` Mcnamara, John
2017-07-31 21:53           ` Thomas Monjalon
2017-07-26 17:02     ` [dpdk-dev] [PATCH v4 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-28 11:57       ` Mcnamara, John
2017-07-26 17:02     ` [dpdk-dev] [PATCH v4 3/3] doc: update mlx guides Shahaf Shuler
2017-07-28 12:07       ` Mcnamara, John
2017-07-26  6:48   ` [dpdk-dev] [PATCH v3 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-26  6:48   ` [dpdk-dev] [PATCH v3 3/3] doc: update mlx guides Shahaf Shuler
2017-07-25 12:07 ` [dpdk-dev] [PATCH v2 2/3] doc: update release notes for mlx driver Shahaf Shuler
2017-07-25 12:07 ` [dpdk-dev] [PATCH v2 3/3] doc: update mlx guides Shahaf Shuler

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=VI1PR05MB31496495F9E00CB5312F8A55C3B80@VI1PR05MB3149.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).