From: Jakub Kicinski <kuba@kernel.org>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Dave Ertman <david.m.ertman@intel.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Daniel Secik <daniel.secik@gooddata.com>,
"Linux regression tracking \(Thorsten Leemhuis\)"
<regressions@leemhuis.info>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
intel-wired-lan@lists.osuosl.org, Igor Raits <igor@gooddata.com>,
Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>
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: Thu, 1 Feb 2024 06:57:26 -0800 [thread overview]
Message-ID: <20240201065726.50a0b1f2@kernel.org> (raw)
In-Reply-To: <898b6ac8-186d-4675-a1e7-abd78b885d01@leemhuis.info>
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
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Dave Ertman <david.m.ertman@intel.com>
Cc: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>,
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: Thu, 1 Feb 2024 06:57:26 -0800 [thread overview]
Message-ID: <20240201065726.50a0b1f2@kernel.org> (raw)
In-Reply-To: <898b6ac8-186d-4675-a1e7-abd78b885d01@leemhuis.info>
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
next prev parent reply other threads:[~2024-02-01 14:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:49 [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 Jaroslav Pulchart
2024-01-10 6:45 ` Jaroslav Pulchart
2024-01-10 18:07 ` Jesse Brandeburg
2024-01-11 8:26 ` Jaroslav Pulchart
2024-01-12 10:23 ` Paul Menzel
2024-01-12 10:23 ` Paul Menzel
2024-01-24 14:29 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-24 16:30 ` Paul Menzel
2024-01-24 16:30 ` Paul Menzel
2024-02-01 14:57 ` Jakub Kicinski [this message]
2024-02-01 14:57 ` Jakub Kicinski
2024-02-01 17:19 ` Jaroslav Pulchart
2024-02-01 17:19 ` Jaroslav Pulchart
2024-02-19 11:29 ` Thorsten Leemhuis
2024-02-19 11:29 ` Thorsten Leemhuis
2024-02-19 11:40 ` Jaroslav Pulchart
2024-02-19 11:40 ` Jaroslav Pulchart
2024-02-22 9:51 ` Thorsten Leemhuis
2024-02-22 9:51 ` Thorsten Leemhuis
2024-03-05 13:00 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-05 13:00 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-14 12:05 ` Igor Raits
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=20240201065726.50a0b1f2@kernel.org \
--to=kuba@kernel.org \
--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=regressions@leemhuis.info \
--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 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.