BPF List
 help / color / mirror / Atom feed
From: Barret Rhoden <brho@google.com>
To: bpf@vger.kernel.org
Cc: Dohyun Kim <dohyunkim@google.com>, Neel Natu <neelnatu@google.com>
Subject: BPF timers in hard irq context?
Date: Tue, 21 May 2024 17:59:07 -0400	[thread overview]
Message-ID: <3faf9614-d61c-47a4-b8ba-6d97ae71fd44@google.com> (raw)

hi -

we've noticed some variability in bpf timer expiration that goes away if 
we change the timers to run in hardirq context.

i imagine the use of softirqs was to keep the potentially long-running 
timer callback out of hardirq, but is there anything particularly 
dangerous about making them run in hardirq?

would you all be open to a patch that makes that a flag or something? 
e.g. BPF_F_TIMER_HARDIRQ.

thanks,

barret

             reply	other threads:[~2024-05-21 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 21:59 Barret Rhoden [this message]
2024-05-22 20:03 ` BPF timers in hard irq context? Alexei Starovoitov
2024-05-23 16:42   ` Barret Rhoden
2024-05-24 20:48     ` Alexei Starovoitov

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=3faf9614-d61c-47a4-b8ba-6d97ae71fd44@google.com \
    --to=brho@google.com \
    --cc=bpf@vger.kernel.org \
    --cc=dohyunkim@google.com \
    --cc=neelnatu@google.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