linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Max Kellermann <max.kellermann@ionos.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Oliver Sang <oliver.sang@intel.com>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	 Linux Memory Management List <linux-mm@kvack.org>,
	linux-kernel@vger.kernel.org, ying.huang@intel.com,
	 feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [linux-next:master] [drivers/char/mem] 1b057bd800: stress-ng.splice.ops_per_sec -99.8% regression
Date: Wed, 18 Oct 2023 10:12:21 +0200	[thread overview]
Message-ID: <CAKPOu+9bZtu80NncqLET_ycZcWynZFHuWGRC4HU2Od9NrsjnCw@mail.gmail.com> (raw)
In-Reply-To: <2023101836-backtalk-mystified-d197@gregkh>

On Wed, Oct 18, 2023 at 9:57 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.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.


  reply	other threads:[~2023-10-18  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 15:06 kernel test robot
2023-10-17 16:56 ` Greg Kroah-Hartman
2023-10-18  6:31   ` Max Kellermann
2023-10-18  7:07   ` Oliver Sang
2023-10-18  7:57     ` Greg Kroah-Hartman
2023-10-18  8:12       ` Max Kellermann [this message]
2023-10-18 10:01     ` Max Kellermann
     [not found] ` <CAKPOu+_T8xk4yd2P4KT4j3eMoFqwYmkxqDHaFtv4Hii5-XyPuA@mail.gmail.com>
2023-10-18 11:12   ` Max Kellermann
2023-10-19  5:41     ` Oliver Sang

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=CAKPOu+9bZtu80NncqLET_ycZcWynZFHuWGRC4HU2Od9NrsjnCw@mail.gmail.com \
    --to=max.kellermann@ionos.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=ying.huang@intel.com \
    /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