[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKPOu+8r1QpFUCyMMS04GOi-+HqM7-dxR4JcoLXfvXARobbZDA@mail.gmail.com>
Date: Wed, 18 Oct 2023 12:01:45 +0200
From: Max Kellermann <max.kellermann@...os.com>
To: Oliver Sang <oliver.sang@...el.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
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:07 AM Oliver Sang <oliver.sang@...el.com> wrote:
> it found a (very big) regression comparing to parent commit.
>
> 19e3e6cdfdc73400 1b057bd800c3ea0c926191d7950
> ---------------- ---------------------------
> %stddev %change %stddev
> \ | \
> 12433266 -99.8% 22893 ą 3% stress-ng.splice.ops_per_sec
Oliver, how is it possible that we have three times the throughput
(MB_per_sec) at 1/500ths the ops?
Powered by blists - more mailing lists