From: Alexey Vlasov <renton@renton.name>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com
Subject: Re: Attaching a process to cgroups
Date: Wed, 8 Aug 2012 20:40:33 +0400 [thread overview]
Message-ID: <20120808164033.GB13735@beaver> (raw)
In-Reply-To: <1343224667.5745.67.camel@marge.simpson.net>
On Wed, Jul 25, 2012 at 03:57:47PM +0200, Mike Galbraith wrote:
> > Hanging on read():
> >
> > # strace -ttT cat /proc/cgroups
> >
> > 17:30:43.825005 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 13), ...}) = 0 <0.000005>
> > 17:30:43.825048 open("/proc/cgroups", O_RDONLY) = 3 <0.000014>
> > 17:30:43.825085 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 <0.000004>
> > 17:30:43.825125 fadvise64(3, 0, 0, POSIX_FADV_SEQUENTIAL) = 0 <0.000005>
> > 17:30:43.825161 read(3, "#subsys_name\thierarchy\tnum_cgrou"..., 32768) = 112 <7.447084>
In general I've changed it to synchronize_rcu_expedited () and all the
delays have gone both on writing and reading files from cgroups.
--
BRGDS. Alexey Vlasov.
next prev parent reply other threads:[~2012-08-08 16:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 18:58 Attaching a process to cgroups Alexey Vlasov
2012-06-20 3:34 ` Daisuke Nishimura
2012-06-20 11:08 ` Alexey Vlasov
2012-06-20 12:28 ` Mike Galbraith
2012-06-21 7:54 ` Alexey Vlasov
2012-06-21 8:23 ` Mike Galbraith
2012-06-21 8:26 ` Mike Galbraith
2012-06-26 18:06 ` Paul E. McKenney
2012-06-27 7:23 ` Mike Galbraith
2012-06-27 17:10 ` Paul E. McKenney
2012-06-28 2:40 ` Mike Galbraith
2012-07-23 20:41 ` Andrea Righi
2012-07-24 1:19 ` Mike Galbraith
2012-07-25 13:36 ` Alexey Vlasov
2012-07-25 13:57 ` Mike Galbraith
2012-07-26 13:02 ` Alexey Vlasov
2012-07-26 14:44 ` Mike Galbraith
2012-08-08 16:40 ` Alexey Vlasov [this message]
2012-08-08 16:51 ` Paul E. McKenney
2012-08-10 9:53 ` Alexey Vlasov
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=20120808164033.GB13735@beaver \
--to=renton@renton.name \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 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.