All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [ANN] netdev round table meeting notes - Sep 22nd
Date: Tue, 22 Sep 2026 11:36:36 -0700	[thread overview]
Message-ID: <20260922113636.2783779a@kernel.org> (raw)

Nebusec bug tracker:
 - https://bugtracker.nebusec.ai/
 - any MAINTAINERS email can log in, feel free to request access 
   if you're an experienced contributor without a MAINTAINERS entry
 - automatic PoC and patch generation
 - needs human review and polish (like all LLM stuff) so maintainers
   encouraged to look thru issues relevant to their code
 - issues auto-closed based on what lands in the tree (not just
   trailers)


NIPA perf testing

Stan:
 - Where do we place the system stats - NIPA or in-tree
Paolo: 
 - Using the CPU metrics is quite noisy, the accounting changes between releases
 - NIPA side would make it faster to change
 - Some of the naming in the patchset is confusing
Stan
 - Let’s keep it simple and start with NIPA
Martin
 - Regression testing is quite difficult, it's not easy to define the
   representative cases
 - Ensure others can plug in their regression tests
Mina
 - We need to avoid over-optimizing for trivial benchmarks
Jakub
 - Would be great to record our preferences about the test quality and
   guidance on what we accept on some wiki page 
Willem
 - How do we store the thresholds, the expectation can fluctuate quite 
   a lot
Jakub
 - Automatic eval in NIPA, same as we do for test case vs HW NIC gating

                 reply	other threads:[~2026-09-22 18:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260922113636.2783779a@kernel.org \
    --to=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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.