From: kernel test robot <lkp@intel.com>
To: wenyang.linux@foxmail.com,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Wen Yang <wenyang.linux@foxmail.com>,
Christoph Hellwig <hch@lst.de>, Dylan Yudaken <dylany@fb.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Paolo Bonzini <pbonzini@redhat.com>, Fu Wei <wefu@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eventfd: support delayed wakeup for non-semaphore eventfd to reduce cpu utilization
Date: Mon, 17 Apr 2023 20:44:41 +0800 [thread overview]
Message-ID: <202304172058.piI49JCE-lkp@intel.com> (raw)
In-Reply-To: <tencent_AF886EF226FD9F39D28FE4D9A94A95FA2605@qq.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on vfs-idmapping/for-next]
[also build test WARNING on linus/master v6.3-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/wenyang-linux-foxmail-com/eventfd-support-delayed-wakeup-for-non-semaphore-eventfd-to-reduce-cpu-utilization/20230416-193353
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping.git for-next
patch link: https://lore.kernel.org/r/tencent_AF886EF226FD9F39D28FE4D9A94A95FA2605%40qq.com
patch subject: [PATCH] eventfd: support delayed wakeup for non-semaphore eventfd to reduce cpu utilization
reproduce:
# https://github.com/intel-lab-lkp/linux/commit/ea9214e265bae223a795f144d6ddcac65e8e2084
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review wenyang-linux-foxmail-com/eventfd-support-delayed-wakeup-for-non-semaphore-eventfd-to-reduce-cpu-utilization/20230416-193353
git checkout ea9214e265bae223a795f144d6ddcac65e8e2084
make menuconfig
# enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
make htmldocs
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304172058.piI49JCE-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/admin-guide/sysctl/fs.rst:74: WARNING: Title underline too short.
vim +74 Documentation/admin-guide/sysctl/fs.rst
72
73 eventfd_wakeup_delay_msec
> 74 ------------------
75 Frequent writing of an eventfd can also lead to frequent wakeup of the peer
76 read process, resulting in significant cpu overhead.
77 How ever for the NON SEMAPHORE eventfd, if it's counter has a nonzero value,
78 then a read(2) returns 8 bytes containing that value, and the counter's value
79 is reset to zero.
80 So it coule be optimized as follows: N event_writes vs ONE event_read.
81 By adding a configurable delay after eventfd_write, these unnecessary wakeup
82 operations are avoided.
83 The max value is 100 ms.
84
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-17 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 11:31 [PATCH] eventfd: support delayed wakeup for non-semaphore eventfd to reduce cpu utilization wenyang.linux
2023-04-17 8:22 ` Bagas Sanjaya
2023-04-17 12:44 ` kernel test robot [this message]
2023-04-17 14:38 ` Jens Axboe
2023-04-17 16:32 ` Wen Yang
2023-04-19 2:15 ` Jens Axboe
2023-04-19 9:12 ` Christian Brauner
2023-04-19 15:23 ` Wen Yang
2023-04-19 16:42 ` Jens Axboe
2023-04-20 17:44 ` Wen Yang
2023-05-04 16:01 ` Wen Yang
[not found] <20230417000711.1100-1-hdanton@sina.com>
2023-04-18 14:12 ` Wen Yang
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=202304172058.piI49JCE-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=dylany@fb.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wefu@redhat.com \
--cc=wenyang.linux@foxmail.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