netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"netdev-driver-reviewers@vger.kernel.org"
	<netdev-driver-reviewers@vger.kernel.org>
Subject: Re: [TEST] Wiki / instructions
Date: Mon, 5 Feb 2024 18:21:56 +0100	[thread overview]
Message-ID: <90c6d9b6-0bc4-468a-95fe-ebc2a23fffc1@kernel.org> (raw)
In-Reply-To: <20240202093148.33bd2b14@kernel.org>

Hi Jakub,

On 02/02/2024 18:31, Jakub Kicinski wrote:
> We added a wiki page to the nipa repo on how to run the tests locally:
> 
> https://github.com/linux-netdev/nipa/wiki/How-to-test-netdev-selftests

Thank you for this wiki page, and all the work with the CI infrastructure!

For the debug options, I see that you are using:

  kernel/configs/x86_debug.config

It looks like this is specific for the 'tip' tree:

  Debugging options for tip tree testing

I don't know if it is still maintained, e.g. it includes DEBUG_SLAB
option. But also, it enables options that are maybe not needed: GCOV?
X86_DEBUG_FPU?
Maybe it is better not to use this .config file, no?

For our CI validating MPTCP tests in a "debug" mode, we use
"debug.config" without "x86_debug.config". On top of that, we also
disable "SLUB_DEBUG_ON", because the impact on the perf is too
important, especially with slow environments. We think it is not worth
it for our case. You don't have the same hardware, but if you have perf
issues, don't hesitate to do the same ;)

> Also feel free to request membership in the linux-netdev org to be able
> to edit!

Linked to the discussion we had last week, I can describe which patches
are being tested if you think it can help others :)

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.
(matttbe on GitHub)

  reply	other threads:[~2024-02-05 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 17:31 [TEST] Wiki / instructions Jakub Kicinski
2024-02-05 17:21 ` Matthieu Baerts [this message]
2024-02-07  1:37   ` Jakub Kicinski
2024-02-07  8:50     ` Matthieu Baerts
2024-02-07 15:21       ` Jakub Kicinski
2024-02-07 15:59         ` Matthieu Baerts
2024-02-08  2:11           ` Jakub Kicinski
2024-02-09 10:25 ` Simon Horman
2024-02-09 15:30   ` Jakub Kicinski
2024-02-16 17:01     ` Simon Horman

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=90c6d9b6-0bc4-468a-95fe-ebc2a23fffc1@kernel.org \
    --to=matttbe@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev-driver-reviewers@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).