[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8b080deb-adcc-4490-8e1d-5be789b1fcff@i-love.sakura.ne.jp>
Date: Thu, 16 Dec 2021 01:02:12 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: kernel test robot <oliver.sang@...el.com>
Cc: Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>,
LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org,
lkp@...el.com, ying.huang@...el.com, feng.tang@...el.com,
zhengjun.xing@...ux.intel.com, fengwei.yin@...el.com
Subject: Re: [loop] e3f9387aea: stress-ng.loop.ops_per_sec 78.9% improvement
On 2021/12/15 22:58, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed a 78.9% improvement of stress-ng.loop.ops_per_sec due to commit:
>
>
> commit: e3f9387aea67742b9d1f4de8e5bb2fd08a8a4584 ("loop: Use pr_warn_once() for loop_control_remove() warning")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
Avoiding printk() flooding will reduce latency, but I'm curious
why the testing program is trying ioctl(fd, LOOP_CTL_REMOVE, -1) ?
Since such ioctl() is pointless, measuring ops_per_sec is also pointless...
Powered by blists - more mailing lists