All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: gowrishankar
	<gomuthuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: iranna.ankad-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org,
	sudhirkumarmalik-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	dhavalgiani-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org,
	risrajak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org,
	Balbir Singh
	<balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [Testing CGROUP inside CONTAINER]: BUG#1
Date: Thu, 04 Dec 2008 05:34:23 -0800	[thread overview]
Message-ID: <1228397664.13111.32.camel@nimitz> (raw)
In-Reply-To: <4937DA54.8060801-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

On Thu, 2008-12-04 at 18:55 +0530, gowrishankar wrote:
> It is expected behaviour of container, as PIDs in other namespaces will 
> always be shown as 0.
> So here, these 0s are from system ns (probably, as you had only system 
> ns and delta ns).

I think it is pretty bogus to be showing the 0's.  It is "expected" only
when we got access to a task which we were not supposed to receive.

Rishi, is this any different in behavior if you do the cgroup mount
after creating the container?

-- Dave

  parent reply	other threads:[~2008-12-04 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04  8:14 [Testing CGROUP inside CONTAINER]: BUG#1 Rishikesh K. Rajak
     [not found] ` <1228378478.4234.35.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-12-04 13:25   ` gowrishankar
     [not found]     ` <4937DA54.8060801-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-12-04 13:12       ` Rishikesh K. Rajak
2008-12-04 13:34       ` Dave Hansen [this message]
2008-12-04 13:42         ` Rishikesh K Rajak

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=1228397664.13111.32.camel@nimitz \
    --to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dhavalgiani-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
    --cc=gomuthuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=iranna.ankad-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
    --cc=risrajak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
    --cc=sudhirkumarmalik-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
    /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.