From: Al Viro <viro@ZenIV.linux.org.uk>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: Timing performance regression 4.15 to 4.16-rc1
Date: Tue, 13 Mar 2018 04:03:54 +0000 [thread overview]
Message-ID: <20180313040354.GW30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <31a4b0d7-2c9e-ce76-a486-48ed18b96cc6@redhat.com>
On Sun, Mar 11, 2018 at 02:02:03PM +0100, Zdenek Kabelac wrote:
> Hi
>
> I've noticed quite some drop of performance (around 15% in some cases) where
> execution of lvm2 tests took longer time - and while tests itself should not
> really load CPU system - the overall running time just got bigger.
>
> Running bisect game pointed clearly to this commit:
>
> ---
>
> commit 44c02a2c3dc55835e9f0d8ef73966406cd805001
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Thu Oct 5 12:59:44 2017 -0400
>
> dev_ioctl(): move copyin/copyout to callers
>
>
> ---
>
> clear revert of this commit on top of 3266b5bd97eaa72793df0b6e5a106c69ccc166c4
> (recent ~4.16-rc4) restored timing of tests back.
>
>
> I'm not sure why - so at this moment this is just a patch causing 15% longer
> running times on lvm2 test suite.
I find it very hard to believe, TBH. It doesn't go anywhere near drivers/md;
could you profile the damn thing and see where does it spend that extra time?
It really doesn't touch anything on non-sockets...
next prev parent reply other threads:[~2018-03-13 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 13:02 Zdenek Kabelac
2018-03-13 4:03 ` Al Viro [this message]
2018-03-13 11:17 ` Zdenek Kabelac
2018-03-13 16:45 ` Zdenek Kabelac
2018-03-13 21:46 ` Zdenek Kabelac
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=20180313040354.GW30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@redhat.com \
--cc=zkabelac@redhat.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
Powered by JetHome