public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Chen Gang <gang.chen@asianux.com>, Li Zefan <lizefan@huawei.com>,
	containers@lists.linux-foundation.org, cgroups@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh
Date: Thu, 21 Nov 2013 10:21:13 +0800	[thread overview]
Message-ID: <528D6E19.4080100@gmail.com> (raw)
In-Reply-To: <20131120173549.GO28946@htj.dyndns.org>

On 11/21/2013 01:35 AM, Tejun Heo wrote:
> Hello,
> 
> Sorry about the delay.
> 

Oh, No problem, every members time resources are expensive, thank you
for your reply.


> On Fri, Nov 08, 2013 at 04:15:23PM +0800, Chen Gang wrote:
>> After simplify, the related operation, environments and output are:
>>
>>   [root@gchenlinux tmp]# df -Th | grep cgroup
>>   tmpfs                             tmpfs    1001M     0 1001M   0% /sys/fs/cgroup
>>   [root@gchenlinux tmp]# lsof | grep cgroup | grep -v grep
>>   systemd       1          root    6r      DIR               0,18         0       5998 /sys/fs/cgroup/systemd/system
>>   [root@gchenlinux tmp]# cat /proc/cgroups 
>>   #subsys_name	hierarchy	num_cgroups	enabled
>>   cpuset	3	4	1
>>   cpu	4	35	1
>>   cpuacct	4	35	1
>>   freezer	5	4	1
>>   [root@gchenlinux tmp]# mkdir cgroup
>>   [root@gchenlinux tmp]# mount -t cgroup -o freezer,cpuacct xxx cgroup/
>>   mount: xxx already mounted or cgroup/ busy
>>
>> Is it real issue of cgroup? If it is, I will/should continue analyzing.
> 
> Hmmm... I'm a bit confused.  What is it testing?  "cat /proc/cgroup"
> is showing that freezer is already mounted and the kernel seems to
> have correctly refused to mount it in a different hierarchy.  What am
> I missing here?
> 

Hmm... I am not quit familiar about it, either, but at least I can
contact related LTP members (I guess they can make sure about it).


Excuse me, I am changing/finding new job, so I should not use Asianux
Corporation mail again.  And it seems I can not be focus on upstream
kernel as much as before.  :-(

But at least, I will/should continue providing some contributions (more
or less) to Public Open Source as volunteers. And for upstream kernel,
I plan to make 1-3 patches per month (mainly for cross compiling).

 - if can not get companies support, I can not provide enough time
   resource on upstream kernel (I have to get pay check for family).

 - New company may mainly focus on open source tool chains (not only
   kernel), so I will/should also provide some contributions to them
   (e.g. KVM, GCC ...).


At last, sorry again for I have to give up 10 patches per month for
upstream kernel.


Thanks.
-- 
Chen Gang

      reply	other threads:[~2013-11-21  2:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  8:15 [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh Chen Gang
2013-11-20 17:35 ` Tejun Heo
2013-11-21  2:21   ` Chen Gang [this message]

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=528D6E19.4080100@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=gang.chen@asianux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox