From: Kirill Tkhai <ktkhai@virtuozzo.com> To: axboe@kernel.dk, bcrl@kvack.org, viro@zeniv.linux.org.uk, tj@kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-aio@kvack.org, oleg@redhat.com, ktkhai@virtuozzo.com Subject: [PATCH 0/5] blkcg: Limit maximum number of aio requests available for cgroup Date: Mon, 04 Dec 2017 19:12:51 +0300 [thread overview] Message-ID: <151240305010.10164.15584502480037205018.stgit@localhost.localdomain> (raw) Hi, this patch set introduces accounting aio_nr and aio_max_nr per blkio cgroup. It may be used to limit number of aio requests, which are available for a cgroup, and could be useful for containers. The accounting is hierarchical, and aio contexts, allocated in child cgroup, are accounted in parent cgroups too. Also, new cgroup file "io.aio_nr" is introduced. It's used to set cgroup aio requests limit, to show current limit and number of currenly occupied requests. Patches 1-3 are refactoring. Patch 4 is the place where the accounting actually introduced. Patch 5 adds "io.aio_nr" file. --- Kirill Tkhai (5): aio: Move aio_nr increment to separate function aio: Export aio_nr_lock and aio_max_nr initial value to include/linux/aio.h blkcg: Add blkcg::blkg_aio_nr and blkcg::blkg_aio_max_nr blkcg: Charge aio requests in blkio cgroup hierarchy blkcg: Add cgroup file to configure blkcg::blkg_aio_max_nr block/blk-cgroup.c | 88 +++++++++++++++++++++++++- fs/aio.c | 151 ++++++++++++++++++++++++++++++++++++++++---- include/linux/aio.h | 21 ++++++ include/linux/blk-cgroup.h | 4 + 4 files changed, 247 insertions(+), 17 deletions(-) -- Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com> -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to majordomo@kvack.org. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
WARNING: multiple messages have this Message-ID (diff)
From: Kirill Tkhai <ktkhai@virtuozzo.com> To: axboe@kernel.dk, bcrl@kvack.org, viro@zeniv.linux.org.uk, tj@kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-aio@kvack.org, oleg@redhat.com, ktkhai@virtuozzo.com Subject: [PATCH 0/5] blkcg: Limit maximum number of aio requests available for cgroup Date: Mon, 04 Dec 2017 19:12:51 +0300 [thread overview] Message-ID: <151240305010.10164.15584502480037205018.stgit@localhost.localdomain> (raw) Hi, this patch set introduces accounting aio_nr and aio_max_nr per blkio cgroup. It may be used to limit number of aio requests, which are available for a cgroup, and could be useful for containers. The accounting is hierarchical, and aio contexts, allocated in child cgroup, are accounted in parent cgroups too. Also, new cgroup file "io.aio_nr" is introduced. It's used to set cgroup aio requests limit, to show current limit and number of currenly occupied requests. Patches 1-3 are refactoring. Patch 4 is the place where the accounting actually introduced. Patch 5 adds "io.aio_nr" file. --- Kirill Tkhai (5): aio: Move aio_nr increment to separate function aio: Export aio_nr_lock and aio_max_nr initial value to include/linux/aio.h blkcg: Add blkcg::blkg_aio_nr and blkcg::blkg_aio_max_nr blkcg: Charge aio requests in blkio cgroup hierarchy blkcg: Add cgroup file to configure blkcg::blkg_aio_max_nr block/blk-cgroup.c | 88 +++++++++++++++++++++++++- fs/aio.c | 151 ++++++++++++++++++++++++++++++++++++++++---- include/linux/aio.h | 21 ++++++ include/linux/blk-cgroup.h | 4 + 4 files changed, 247 insertions(+), 17 deletions(-) -- Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
next reply other threads:[~2017-12-04 16:12 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-04 16:12 Kirill Tkhai [this message] 2017-12-04 16:12 ` [PATCH 0/5] blkcg: Limit maximum number of aio requests available for cgroup Kirill Tkhai 2017-12-04 16:12 ` [PATCH 1/5] aio: Move aio_nr increment to separate function Kirill Tkhai 2017-12-04 16:13 ` [PATCH 2/5] aio: Export aio_nr_lock and aio_max_nr initial value to include/linux/aio.h Kirill Tkhai 2017-12-04 16:13 ` [PATCH 3/5] blkcg: Add blkcg::blkg_aio_nr and blkcg::blkg_aio_max_nr Kirill Tkhai 2017-12-04 16:13 ` [PATCH 4/5] blkcg: Charge aio requests in blkio cgroup hierarchy Kirill Tkhai 2017-12-04 16:13 ` [PATCH 5/5] blkcg: Add cgroup file to configure blkcg::blkg_aio_max_nr Kirill Tkhai 2017-12-04 16:52 ` [PATCH 0/5] blkcg: Limit maximum number of aio requests available for cgroup Benjamin LaHaise 2017-12-04 21:27 ` Kirill Tkhai 2017-12-04 21:35 ` Jeff Moyer 2017-12-04 21:35 ` Jeff Moyer 2017-12-04 21:48 ` Kirill Tkhai 2017-12-04 20:07 ` Tejun Heo 2017-12-04 21:44 ` Kirill Tkhai 2017-12-04 21:52 ` Tejun Heo 2017-12-04 22:49 ` Kirill Tkhai 2017-12-04 22:59 ` Jeff Moyer 2017-12-04 22:59 ` Jeff Moyer 2017-12-04 23:14 ` Kirill Tkhai 2017-12-05 15:41 ` Jeff Moyer 2017-12-05 15:41 ` Jeff Moyer 2017-12-05 15:51 ` Tejun Heo 2017-12-04 23:02 ` Tejun Heo 2017-12-04 23:05 ` Kirill Tkhai 2017-12-05 15:19 ` Oleg Nesterov 2017-12-05 15:35 ` Benjamin LaHaise 2017-12-06 17:32 ` Oleg Nesterov 2017-12-06 17:44 ` Benjamin LaHaise 2017-12-06 17:44 ` Benjamin LaHaise 2017-12-06 18:19 ` Kirill Tkhai 2017-12-06 18:30 ` Benjamin LaHaise 2017-12-06 19:37 ` Kirill Tkhai 2017-12-07 13:44 ` Oleg Nesterov
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=151240305010.10164.15584502480037205018.stgit@localhost.localdomain \ --to=ktkhai@virtuozzo.com \ --cc=axboe@kernel.dk \ --cc=bcrl@kvack.org \ --cc=linux-aio@kvack.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=oleg@redhat.com \ --cc=tj@kernel.org \ --cc=viro@zeniv.linux.org.uk \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.