mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Juraj Šarinay" <juraj@sarinay.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
	edumazet@google.com,  kuba@kernel.org, pabeni@redhat.com,
	mingo@kernel.org, horms@kernel.org,  tglx@linutronix.de
Subject: Re: [PATCH net-next v2] net: nfc: nci: Turn data timeout into a module parameter and increase the default
Date: Wed, 27 Aug 2025 19:48:33 +0200	[thread overview]
Message-ID: <518333811aeda4dc42445efd6d9cee6cc580145a.camel@sarinay.com> (raw)
In-Reply-To: <c0c14ec0-f582-4e26-bc7e-35a26a7ff1ce@kernel.org>

On Wed, 2025-08-27 at 15:29 +0200, Krzysztof Kozlowski wrote:

> CardOS is the software running on the NFC card, right? 

Yes it is. I may have been too specific, all I am saying is that I made
some measurements.

> If so, why would this be Linux kernel module param? Kernel runtime setup is really
> independent of what NFC card people will use.

I suggested a tunable timeout because I am not sure what the new
universal upper bound should be. It may depend on the NFC card one is
communicating with. I have since learned that module parameters are
strongly discouraged (within netdev at least).

> I think this should be unconditionally raised

I am fine with that, but would argue for an even more generous timeout.
Five seconds, say? One can always set a shorter SO_RCVTIMEO from user
space if needed.

Ideally, the kernel would also honor a longer SO_RCVTIMEO and treat
NCI_DATA_TIMEOUT as a default rather than a rigid limit, completely
obviating my subjective need for a parameter. I have not explored the
idea further, given that a somewhat higher value of NCI_DATA_TIMEOUT
solves most problems.

Best,
Juraj

      reply	other threads:[~2025-08-27 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 23:43 Juraj Šarinay
2025-08-27 13:29 ` Krzysztof Kozlowski
2025-08-27 17:48   ` Juraj Šarinay [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=518333811aeda4dc42445efd6d9cee6cc580145a.camel@sarinay.com \
    --to=juraj@sarinay.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tglx@linutronix.de \
    /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®