mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: michael.chan@broadcom.com, linux-kernel@vger.kernel.org,
	dave.jiang@intel.com, saeedm@nvidia.com,
	Jonathan.Cameron@huawei.com, gospo@broadcom.com,
	selvin.xavier@broadcom.com, leon@kernel.org,
	kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH v5 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device
Date: Fri, 13 Mar 2026 15:17:03 -0300	[thread overview]
Message-ID: <20260313181703.GI1704121@ziepe.ca> (raw)
In-Reply-To: <CALs4sv2V8ZTfQ2HCCD9U3RJCyhgpDjYXp+H3gTE9z6rqhX+jOw@mail.gmail.com>

On Fri, Mar 13, 2026 at 11:44:05PM +0530, Pavan Chebbi wrote:
> >
> > Timeout is such a complicated thing to add to a HW RPC interface. Does
> > bnxt do it right? Claude says no, and it looks compelling to me..
> >
> > So don't give userspace an easy ability to trigger timeout, by
> > lowering the timeout value, and causing corruption in the kernel.
> 
> Yea I see what you are saying. I think it should be fine if
> bnxtctl_fw_rpc() itself increases the timeout for the required
> commands.

Ah, you wanted to increase the timeout - yes, I think the kernel needs
to do this itself to avoid userspace triggering timeouts that don't
work right..

> I can make this change. But if I drop the "timeout" now, I won't need
> the driver_data we discussed previously, at least until I actually add
> the future enhancements.
> So I guess I should defer that change to when I actually use
> driver_data, right?

Yes all that makes sense. Without timeout and the dma list thing there
is no reason to wrapper the commands. Comme with some driver_data
later if you find you need more info

Jason




  reply	other threads:[~2026-03-13 18:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26  8:23 [PATCH v5 fwctl 0/5] fwctl/bnxt_fwctl: fwctl for Broadcom Netxtreme devices Pavan Chebbi
2026-02-26  8:23 ` [PATCH v5 fwctl 1/5] fwctl/bnxt_en: Move common definitions to include/linux/bnxt/ Pavan Chebbi
2026-02-26  8:23 ` [PATCH v5 fwctl 2/5] fwctl/bnxt_en: Refactor aux bus functions to be more generic Pavan Chebbi
2026-03-13 15:46   ` Jason Gunthorpe
2026-03-13 15:57     ` Pavan Chebbi
2026-02-26  8:23 ` [PATCH v5 fwctl 3/5] fwctl/bnxt_en: Create an aux device for fwctl Pavan Chebbi
2026-02-26  8:23 ` [PATCH v5 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device Pavan Chebbi
2026-03-13 16:06   ` Jason Gunthorpe
2026-03-13 17:56     ` Pavan Chebbi
2026-03-13 16:14   ` Jason Gunthorpe
2026-03-13 18:14     ` Pavan Chebbi
2026-03-13 18:17       ` Jason Gunthorpe [this message]
2026-02-26  8:23 ` [PATCH v5 fwctl 5/5] fwctl/bnxt_fwctl: Add documentation entries Pavan Chebbi

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=20260313181703.GI1704121@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=dave.jiang@intel.com \
    --cc=gospo@broadcom.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=pavan.chebbi@broadcom.com \
    --cc=saeedm@nvidia.com \
    --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

all inboxes | Powered by JetHome®