Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Selvin Xavier <selvin.xavier@broadcom.com>,
	andrew.gospodarek@broadcom.com
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
	kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH for-next v2] RDMA/bnxt_re: Congestion control settings using debugfs hook
Date: Tue, 21 Jan 2025 11:31:27 -0400	[thread overview]
Message-ID: <20250121153127.GQ674319@ziepe.ca> (raw)
In-Reply-To: <CA+sbYW2oDbrodgYdzOgUiSv6v+8aBcACLbfrXM+0NZGmHquUFw@mail.gmail.com>

On Tue, Jan 21, 2025 at 04:10:33PM +0530, Selvin Xavier wrote:
> On Mon, Jan 20, 2025 at 10:10 PM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> >
> > On Sun, Jan 19, 2025 at 07:45:35AM -0800, Selvin Xavier wrote:
> > > Implements routines to set and get different settings  of
> > > the congestion control. This will enable the users to modify
> > > the settings according to their network.
> >
> > Should something like this be in debugfs though?
> Since these are Broadcom specific parameters, i thought its better to
> be under debugfs. Also I took the reference of a similar
> implementation in mlx5.

debugfs is disabled in a lot of deployments, it is a big part of why
we are doing fwctl. If you know it works for you cases, debugfs is
pretty open ended..

> > bnxt_qplib_modify_cc() is just sending a firmware command, seems like
> > this should belong to fwctl?
> Agree. We can move to this model once fwctl is accepted. For now, it
> is important for us to support our customers with an immediate
> solution. Customers are asking for this support.

Well, fwctl can be accepted when you guys come through with an
implementation :)
 
> > Additionally there may be interest in some common way to control CC
> > for RDMA..
> 
> Do you think there are common parameters for multiple vendors here? I
> think enable/disable is an option.

I haven't seen much commonality here, every site seems to have their
own totally different stuff right now.

Jason

  reply	other threads:[~2025-01-21 15:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19 15:45 [PATCH for-next v2] RDMA/bnxt_re: Congestion control settings using debugfs hook Selvin Xavier
2025-01-20 16:40 ` Jason Gunthorpe
2025-01-21 10:40   ` Selvin Xavier
2025-01-21 15:31     ` Jason Gunthorpe [this message]
2025-01-22  8:09       ` Selvin Xavier
2025-01-22 15:22         ` Jason Gunthorpe
2025-01-23  5:20           ` Selvin Xavier
2025-02-03 12:02 ` Leon Romanovsky
2025-02-03 12:03 ` Leon Romanovsky
2025-02-08  9:19 ` Chengchang Tang
2025-02-08 13:14   ` Selvin Xavier

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=20250121153127.GQ674319@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=selvin.xavier@broadcom.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