[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKPOu+9bZtu80NncqLET_ycZcWynZFHuWGRC4HU2Od9NrsjnCw@mail.gmail.com>
Date: Wed, 18 Oct 2023 10:12:21 +0200
From: Max Kellermann <max.kellermann@...os.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Oliver Sang <oliver.sang@...el.com>, oe-lkp@...ts.linux.dev,
lkp@...el.com, Linux Memory Management List <linux-mm@...ck.org>,
linux-kernel@...r.kernel.org, ying.huang@...el.com,
feng.tang@...el.com, fengwei.yin@...el.com
Subject: Re: [linux-next:master] [drivers/char/mem] 1b057bd800:
stress-ng.splice.ops_per_sec -99.8% regression
On Wed, Oct 18, 2023 at 9:57 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> That's odd given that as was pointed out, this test does not even touch
> the code paths that this patch changed.
I think I mixed up the "vmsplice" and the "splice" tests, and my
conclusion was wrong, sorry.
This performance regression is about the "splice" test which indeed
uses /dev/zero. I'll have a closer look and get back to you.
Powered by blists - more mailing lists