public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@nvidia.com>
To: "kuba@kernel.org" <kuba@kernel.org>
Cc: Shay Drory <shayd@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v3 0/7] net/mlx5: Memory optimizations
Date: Wed, 15 Dec 2021 18:26:37 +0000	[thread overview]
Message-ID: <c55710e02f732b46fa5c48bb65b7eab23ee3c5ce.camel@nvidia.com> (raw)
In-Reply-To: <20211213170146.24676fa8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Mon, 2021-12-13 at 17:01 -0800, Jakub Kicinski wrote:
> On Mon, 13 Dec 2021 23:06:26 +0000 Saeed Mahameed wrote:
> > On Wed, 2021-12-08 at 16:17 +0200, Shay Drory wrote:
> > > This series provides knobs which will enable users to
> > > minimize memory consumption of mlx5 Functions (PF/VF/SF).
> > > mlx5 exposes two new generic devlink params for EQ size
> > > configuration and uses devlink generic param max_macs.
> > > 
> > > Patches summary:
> > >  - Patch-1 Introduce log_max_current_uc_list_wr_supported bit 
> > >  - Patches-2-3 Provides I/O EQ size param which enables to save
> > >    up to 128KB.
> > >  - Patches-4-5 Provides event EQ size param which enables to save
> > >    up to 512KB.
> > >  - Patch-6 Clarify max_macs param.
> > >  - Patch-7 Provides max_macs param which enables to save up to
> > > 70KB
> > > 
> > > In total, this series can save up to 700KB per Function.
> > 
> > Jakub are ok with this version ?
> > I would like to take it to my trees.
> 
> Yup, go for it. Sorry I didn't ack - I was going to apply it today
> but
> Dave reminded me that you probably want to take it thru your tree.

Thanks ! applied. Will be sent in future PRs.
First patch needs to go to mlx5-next shared branch with rdma.
So this will be sent in two separate PRs.







      reply	other threads:[~2021-12-15 18:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 14:17 [PATCH net-next v3 0/7] net/mlx5: Memory optimizations Shay Drory
2021-12-08 14:17 ` [PATCH net-next v3 1/7] net/mlx5: Introduce log_max_current_uc_list_wr_supported bit Shay Drory
2021-12-08 14:17 ` [PATCH net-next v3 2/7] devlink: Add new "io_eq_size" generic device param Shay Drory
2021-12-09  9:21   ` Jiri Pirko
2021-12-08 14:17 ` [PATCH net-next v3 3/7] net/mlx5: Let user configure io_eq_size param Shay Drory
2021-12-08 14:17 ` [PATCH net-next v3 4/7] devlink: Add new "event_eq_size" generic device param Shay Drory
2021-12-09  9:22   ` Jiri Pirko
2021-12-08 14:17 ` [PATCH net-next v3 5/7] net/mlx5: Let user configure event_eq_size param Shay Drory
2021-12-08 14:17 ` [PATCH net-next v3 6/7] devlink: Clarifies max_macs generic devlink param Shay Drory
2021-12-08 14:17 ` [PATCH net-next v3 7/7] net/mlx5: Let user configure max_macs generic param Shay Drory
2021-12-13 23:06 ` [PATCH net-next v3 0/7] net/mlx5: Memory optimizations Saeed Mahameed
2021-12-14  1:01   ` Jakub Kicinski
2021-12-15 18:26     ` Saeed Mahameed [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=c55710e02f732b46fa5c48bb65b7eab23ee3c5ce.camel@nvidia.com \
    --to=saeedm@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shayd@nvidia.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