All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Kanzenbach <kurt@linutronix.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	jan.kiszka@siemens.com, vivek.behera@siemens.com
Subject: Re: [PATCH net-next] net/core: Enable socket busy polling on -RT
Date: Wed, 08 Nov 2023 08:41:34 +0100	[thread overview]
Message-ID: <87bkc44rpt.fsf@kurt> (raw)
In-Reply-To: <fc7fb885df3a52d076bb71191afa786d19d79cd5.camel@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

Hi Florian,

On Mon Oct 30 2023, Florian Bezdeka wrote:
>> > > Allow RX_BUSY_POLL on PREEMPT_RT if NETPOLL is disabled. Don't disable
>> > > preemption on PREEMPT_RT within the busy poll loop.
>
> Sorry, I need one more information here: We try to re-use the kernel
> and its configuration from Debian whenever possible. NETPOLL/NETCONSOLE
> is build as module there.
>
> Will this limitation be addressed in the future? Is someone already
> working on that? Is that maybe on the radar for the ongoing printk()
> work? (Assuming printk() with NETCONSOLE enabled is the underlying
> problem)
>
> We don't use NETPOLL/NETCONSOLE during runtime but it is enabled at
> build time. Sadly we can not use busy polling mode in combination with
> XDP now. (Ignoring the fact that we could adjust the kernel
> configuration, build on our own, ...)
>
> Would love to hear your thoughts about that. Thanks a lot!

Yes, the busy polling conflicts with netpoll due to the locking. At the
moment you have to disable it in the kernel configuration and
re-compile. I don't think anyone is working on solving this limitation
yet.

Thanks,
Kurt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

      reply	other threads:[~2023-11-08  7:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 11:15 [PATCH net-next] net/core: Enable socket busy polling on -RT Kurt Kanzenbach
2023-05-25 11:16 ` Paolo Abeni
2023-05-25 13:49   ` Sebastian Andrzej Siewior
2023-05-26  8:00 ` patchwork-bot+netdevbpf
2023-10-27 11:43 ` Florian Bezdeka
2023-10-28 10:09   ` Kurt Kanzenbach
2023-10-30 11:29     ` Florian Bezdeka
2023-11-08  7:41       ` Kurt Kanzenbach [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=87bkc44rpt.fsf@kurt \
    --to=kurt@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vivek.behera@siemens.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.