From: Jens Axboe <jens.axboe@oracle.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] Do not delete cgroups upon completion of fio job
Date: Wed, 31 Mar 2010 19:26:00 +0200 [thread overview]
Message-ID: <20100331172600.GC23510@kernel.dk> (raw)
In-Reply-To: <20100331171931.GH14011@redhat.com>
On Wed, Mar 31 2010, Vivek Goyal wrote:
> Currently upon fio job completion, we delete the cgroups. But in the
> process we also loose important debugging information presetn in cgroup
> files. For example time information in blkio.time, sector information in
> blkio.sectors and how many a times a group was dequeued blkio.dequeue.
> Leaving the cgroups as it is, allows one to go and inspect those files
> after the fio job is complete.
>
> Secondly, cgroups might have already been created by user before fio job
> started. In that case it is not very right to delete cgroups after job
> completion.
Confused, I was pretty sure that I added code back then to only delete
cgroups when they were created by fio. Checking, that is what it should
do - we only add the cgroup to the kill list, if we were the one to
create it. That was on purpose, since I did not want to leave them
around.
I'd suggest adding a specific option to NOT kill a cgroup. Or you could
have a post_exec option that tar's up the contents of that directory,
perhaps even formalized?
--
Jens Axboe
next prev parent reply other threads:[~2010-03-31 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 17:19 [PATCH] Do not delete cgroups upon completion of fio job Vivek Goyal
2010-03-31 17:26 ` Jens Axboe [this message]
2010-03-31 17:35 ` Vivek Goyal
2010-03-31 17:38 ` Jens Axboe
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=20100331172600.GC23510@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fio@vger.kernel.org \
--cc=vgoyal@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