DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: add support for PF representor
Date: Thu, 18 Apr 2019 18:54:57 +0000	[thread overview]
Message-ID: <AM6PR0502MB379761761955B607509FDAA9C3260@AM6PR0502MB3797.eurprd05.prod.outlook.com> (raw)
Message-ID: <20190418185457.ptzrtgjm18hCF2QpBDnSmE1aXDVIuaY12SJdbvspAsg@z> (raw)
In-Reply-To: <1555423828-31859-1-git-send-email-viacheslavo@mellanox.com>

Tuesday, April 16, 2019 5:10 PM, Viacheslav Ovsiienko:
> Subject: [dpdk-dev] [PATCH v2] net/mlx5: add support for PF representor
> 
> On BlueField platform we have the new entity - PF representor.
> This one represents the PCI PF attached to external host on the side of ARM.
> The traffic sent by the external host to the NIC via PF will be seem by ARM on
> this PF representor.
> 
> This patch refactors port recognizing capability on the base of physical port
> name. We have two groups of name formats. Legacy name formats are
> supported by kernels before ver 5.0 (being more precise - before the patch
> [1]) or before Mellanox OFED 4.6, and new naming formats added by the
> patch [1].
> 
> Legacy naming formats are supported:
> 
>   - missing physical port name (no sysfs/netlink key) at all,
>     master is assumed
> 
>   - decimal digits (for example "12"), representor is assumed,
>     the value is the index of attached VF
> 
> New naming formats are supported:
> 
>   - "p" followed by decimal digits, for example "p2", master
>     is assumed
> 
>   - "pf" followed by PF index concatenated with "vf" followed by
>     VF index, for example "pf0vf1", representor is assumed.
>     If index of VF is "-1" it is a special case  of host PF
>     representor, this representor must be indexed in devargs
>     as 65535, for example representor=[0-3,65535] will
>     allow representors for VF0, VF1, VF2, VF3 and for host PF.
> 
>     Note: do not specify representor=[0-65535], it causes devargs
>     processing error, because number of ports (rte_eth_dev) is
>     limited.
> 
> Applications should distinguish representors and master devices exclusively
> by device flag RTE_ETH_DEV_REPRESENTOR and do not rely on switch
> port_id (mlx5 PMD deduces ones from representor_id) values returned by
> dev_infos_get() API.
> 
> [1]
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
> .spinics.net%2Flists%2Fnetdev%2Fmsg547007.html&amp;data=02%7C01%7C
> shahafs%40mellanox.com%7C95dc9265aee344ca1c1108d6c27553f3%7Ca6529
> 71c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636910206515011521&amp;sd
> ata=xJFDvK63LaQB9B8eVNn8iKfH5YzsnLW%2FsN1wPh6iyK8%3D&amp;reser
> ved=0
>     Linux-tree: c12ecc23 (Or Gerlitz 2018-04-25 17:32 +0300)
>     "net/mlx5e: Move to use common phys port names for vport
> representors"
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

Applied to next-net-mlx, thanks. 

  parent reply	other threads:[~2019-04-18 18:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 15:48 [dpdk-dev] [PATCH 1/1] " Viacheslav Ovsiienko
2019-04-12 15:48 ` Viacheslav Ovsiienko
2019-04-14  7:42 ` Shahaf Shuler
2019-04-14  7:42   ` Shahaf Shuler
2019-04-15  9:11   ` Slava Ovsiienko
2019-04-15  9:11     ` Slava Ovsiienko
2019-04-16  5:43     ` Shahaf Shuler
2019-04-16  5:43       ` Shahaf Shuler
2019-04-16 14:10 ` [dpdk-dev] [PATCH v2] " Viacheslav Ovsiienko
2019-04-16 14:10   ` Viacheslav Ovsiienko
2019-04-18 14:26   ` Dekel Peled
2019-04-18 14:26     ` Dekel Peled
2019-04-18 18:54   ` Shahaf Shuler [this message]
2019-04-18 18:54     ` 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=AM6PR0502MB379761761955B607509FDAA9C3260@AM6PR0502MB3797.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=viacheslavo@mellanox.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).