All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Saeed Mahameed <saeed@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jason Gunthorpe <jgg@nvidia.com>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	David Ahern <dsahern@kernel.org>,
	Jacob Keller <jacob.e.keller@intel.com>,
	Sridhar Samudrala <sridhar.samudrala@intel.com>,
	david.m.ertman@intel.com, dan.j.williams@intel.com,
	kiran.patil@intel.com, gregkh@linuxfoundation.org
Subject: Re: [net-next v3 00/14] Add mlx5 subfunction support
Date: Sun, 13 Dec 2020 14:08:48 +0200	[thread overview]
Message-ID: <20201213120848.GB5005@unreal> (raw)
In-Reply-To: <20201212122518.1c09eefe@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Sat, Dec 12, 2020 at 12:25:18PM -0800, Jakub Kicinski wrote:
> On Fri, 11 Dec 2020 22:12:11 -0800 Saeed Mahameed wrote:
> > Hi Dave, Jakub, Jason,
> >
> > This series form Parav was the theme of this mlx5 release cycle,
> > we've been waiting anxiously for the auxbus infrastructure to make it into
> > the kernel, and now as the auxbus is in and all the stars are aligned, I
> > can finally submit this V2 of the devlink and mlx5 subfunction support.
> >
> > Subfunctions came to solve the scaling issue of virtualization
> > and switchdev environments, where SRIOV failed to deliver and users ran
> > out of VFs very quickly as SRIOV demands huge amount of physical resources
> > in both of the servers and the NIC.
> >
> > Subfunction provide the same functionality as SRIOV but in a very
> > lightweight manner, please see the thorough and detailed
> > documentation from Parav below, in the commit messages and the
> > Networking documentation patches at the end of this series.
> >
> > Sending V2/V3 as a continuation to V1 that was sent Last month [0],
> > [0] https://lore.kernel.org/linux-rdma/20201112192424.2742-1-parav@nvidia.com/
>
> This adds more and more instances of the 32 bit build warning.
>
> The warning was also reported separately on netdev after the recent
> mlx5-next pull.
>
> Please address that first (or did you already do and I missed it
> somehow?)

Hi Jakub,

I posted a fix from Parav,
https://lore.kernel.org/netdev/20201213120641.216032-1-leon@kernel.org/T/#u

Thanks

  reply	other threads:[~2020-12-13 12:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12  6:12 [net-next v3 00/14] Add mlx5 subfunction support Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 01/14] devlink: Prepare code to fill multiple port function attributes Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 02/14] devlink: Introduce PCI SF port flavour and port attribute Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 03/14] devlink: Support add and delete devlink port Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 04/14] devlink: Support get and set state of port function Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 05/14] net/mlx5: Introduce vhca state event notifier Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 06/14] net/mlx5: SF, Add auxiliary device support Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 07/14] net/mlx5: SF, Add auxiliary device driver Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 08/14] net/mlx5: E-switch, Prepare eswitch to handle SF vport Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 09/14] net/mlx5: E-switch, Add eswitch helpers for " Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 10/14] net/mlx5: SF, Add port add delete functionality Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 11/14] net/mlx5: SF, Port function state change support Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 12/14] devlink: Add devlink port documentation Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 13/14] devlink: Extend devlink port documentation for subfunctions Saeed Mahameed
2020-12-12  6:12 ` [net-next v3 14/14] net/mlx5: Add devlink subfunction port documentation Saeed Mahameed
2020-12-12 20:25 ` [net-next v3 00/14] Add mlx5 subfunction support Jakub Kicinski
2020-12-13 12:08   ` Leon Romanovsky [this message]
2020-12-14  3:25     ` Parav Pandit
2020-12-14 20:06       ` Saeed Mahameed

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=20201213120848.GB5005@unreal \
    --to=leonro@nvidia.com \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=david.m.ertman@intel.com \
    --cc=dsahern@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jgg@nvidia.com \
    --cc=kiran.patil@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeed@kernel.org \
    --cc=sridhar.samudrala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.