From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Dave Ertman <david.m.ertman@intel.com>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Igor Raits <igor@gooddata.com>,
Daniel Secik <daniel.secik@gooddata.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [REGRESSION] Intel ICE Ethernet driver in linux >= 6.6.9 triggers extra memory consumption and cause continous kswapd* usage and continuous swapping
Date: Tue, 5 Mar 2024 14:00:53 +0100 [thread overview]
Message-ID: <d05966fc-7daa-42a9-a125-ffc1478be430@leemhuis.info> (raw)
In-Reply-To: <f41bcb25-0f22-4018-851f-a70ca841cf34@leemhuis.info>
On 22.02.24 10:51, Thorsten Leemhuis wrote:
> On 19.02.24 12:40, Jaroslav Pulchart wrote:
>> If the question is for me then my opinion about it is this:
>>
>> I'm fine with the behaviour of a driver about memory consumption if it
>> is predictable/described with the possibility to change it from
>> default values. My understanding of "predictable" is something like
>> this:
>>
>> The ICE driver is going to
>> * Setup 64 queues per each port, not active included.
>> * Each queue consumes "xxxx MB" amount of kernel memory per each numa node.
>> example: Two 2 ports Intel NICs using ICE driver will consume ~6GB of
>> RAM of each NUMA node, please consider changing the defaults values to
>> avoid OOM :-).
> [...]
> Whatever: to me it still feels like this regression is not handled as
> Linus would want it, but I'm not totally sure and guess I have to admit
> that I'm out of my depth here. I'll let my regression tracking bot
> continue monitor this, but will most likely leave things to the network
> and driver maintainers from here on unless something changes.
FWIW, it seems nobody really cares, so I'll strop tracking this issue:
#regzbot inconclusive: might not qualify as a regression
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
>> po 19. 2. 2024 v 12:29 odesílatel Thorsten Leemhuis
>> <regressions@leemhuis.info> napsal:
>>>
>>> On 01.02.24 18:19, Jaroslav Pulchart wrote:
>>>>>
>>>>> On Wed, 24 Jan 2024 15:29:38 +0100 Linux regression tracking (Thorsten
>>>>> Leemhuis) wrote:
>>>>>>>> I think that's a bad bisect. There is no reason I could understand for
>>>>>>>> that change to cause a continuous or large leak, it really doesn't make
>>>>>>>> any sense. Reverting it consistently helps? You're not just rewinding
>>>>>>>> the tree back to that point, right? just running 6.6.9 without that
>>>>>>>> patch? (sorry for being pedantic, just trying to be certain)
>>>>>>>
>>>>>>> Reverting just the single bisected commit continuously helps for >=
>>>>>>> 6.6.9 and as well for current 6.7.
>>>>>>> We cannot use any new linux kernel without reverting it due to this
>>>>>>> extra memory utilization.
>>>>>>
>>>>>> Quick query: what's the status wrt to this regression? Looks like
>>>>>> nothing happened in the past week.
>>>>>
>>>>> Is someone working on this? Indeed the commit in question looks
>>>>> harmless but can't argue with the revert helping :S
>>>>
>>>> No clue if someone is working on it,
>>>
>>> Yeah, a quick public status update would be really helpful. And maybe
>>> some debugging tips that might enable Jaroslav to pinpoint the real
>>> problem.
>>>
>>>> however the commit itself is a
>>>> trigger of some other issue.
>>>>
>>>> The analysis of my colleague Igor (see previous email) shows the
>>>> memory consumption is caused by queues of each ice network interface
>>>> (even the unused ones). Our final fix was to lower the queues to 6 for
>>>> used interfaces and 2 of unused interfaces manually.
>>>
>>> Despite the above allow me to ask: Can you live with that workaround?
>>> Ideally of course this should be fixed, but well, the world sometimes is
>>> a tricky place. :-/
>>>
>>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>>> --
>>> Everything you wanna know about Linux kernel regression tracking:
>>> https://linux-regtracking.leemhuis.info/about/#tldr
>>> If I did something stupid, please tell me, as explained on that page.
>>>
>>> #regzbot poke
>>
>>
>
>
next prev parent reply other threads:[~2024-03-05 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK8fFZ7Xi3=1HFY400firmpRWzHDPsi90cUU5bjOkF00KNZWeA@mail.gmail.com>
[not found] ` <bce78734-d359-499b-9693-05549e6a73a4@intel.com>
[not found] ` <CAK8fFZ6PqCwgt1n4iuROs=76esQVSOS-HHL=0eN7+efeKT25Uw@mail.gmail.com>
2024-01-12 10:23 ` [Intel-wired-lan] [REGRESSION] Intel ICE Ethernet driver in linux >= 6.6.9 triggers extra memory consumption and cause continous kswapd* usage and continuous swapping Paul Menzel
[not found] ` <898b6ac8-186d-4675-a1e7-abd78b885d01@leemhuis.info>
2024-01-24 16:30 ` Paul Menzel
2024-02-01 14:57 ` Jakub Kicinski
2024-02-01 17:19 ` Jaroslav Pulchart
2024-02-19 11:29 ` Thorsten Leemhuis
2024-02-19 11:40 ` Jaroslav Pulchart
2024-02-22 9:51 ` Thorsten Leemhuis
2024-03-05 13:00 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-01-19 10:23 ` Linux regression tracking (Thorsten Leemhuis)
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=d05966fc-7daa-42a9-a125-ffc1478be430@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=anthony.l.nguyen@intel.com \
--cc=daniel.secik@gooddata.com \
--cc=david.m.ertman@intel.com \
--cc=igor@gooddata.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jaroslav.pulchart@gooddata.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).