From: Cyrill Gorcunov <gorcunov@openvz.org>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, akpm@linuxfoundation.org,
avagin@virtuozzo.com, xemul@virtuozzo.com,
mtk.manpages@gmail.com, kir@openvz.org, gorcunov@openvz.org
Subject: [patch 0/3] fs,epoll: Add ability to call kcmp to find target files
Date: Fri, 10 Mar 2017 11:16:55 +0300 [thread overview]
Message-ID: <20170310081655.462925968@openvz.org> (raw)
Hi! This is slightly updated series for epoll extension
in procfs and kcmp syscall. The procfs patch and manpage
is unchanged while kcmp syscall is slightly updated to
drop hard to read if()'s and shrink memory pressue with
kcmp_epoll_slot argument.
Please take a look, once time permit. Being playing with
this patches via criu directly, works as expected.
https://lists.openvz.org/pipermail/criu/2017-February/036031.html
reply other threads:[~2017-03-10 8:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170310081655.462925968@openvz.org \
--to=gorcunov@openvz.org \
--cc=akpm@linuxfoundation.org \
--cc=avagin@virtuozzo.com \
--cc=kir@openvz.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).