From: Balbir Singh <balbir@in.ibm.com>
To: rohitseth@google.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
devel@openvz.org, CKRM-Tech <ckrm-tech@lists.sourceforge.net>
Subject: Re: [ckrm-tech] [patch 0/5]-Containers: Introduction
Date: Mon, 18 Sep 2006 23:38:05 +0530 [thread overview]
Message-ID: <450EE085.5000704@in.ibm.com> (raw)
In-Reply-To: <1158595571.18533.5.camel@galaxy.corp.google.com>
Rohit Seth wrote:
> On Mon, 2006-09-18 at 18:57 +0530, Balbir Singh wrote:
>> Rohit Seth wrote:
>>
>>> Below is a one line description for patches that will follow:
>>>
>>> [patch01]: Documentation on how to use containers
>>> (Documentation/container.txt)
>>>
>>> [patch02]: Changes in the generic part of kernel code
>>>
>>> [patch03]: Container's interface with configfs
>>>
>>> [patch04]: Core container support
>>>
>>> [patch05]: Over the limit memory handler.
>>>
>> Hi, Rohit,
>>
>> The patches are hard to follow - are they diff'ed with Naurp?
>> At certain places I cannot figure out which function has changed.
>>
>
> They are without p option so the function name is not there. Though
> there is only one patch 02 of 05 that modifies existing code. And that
> too almost all single line changes are starting with container API
> container_* Please let me know if there is something specific that is
> not clear.
>
Patch 02 is hard to read. I was trying to understand the changes made
in the patch. Patch 01 is trivial, I got stuck at 02.
> I will send the next version of patches and I will include -p option as
> well.
>
> thanks,
> -rohit
>
--
Warm Regards,
Balbir Singh,
Linux Technology Center,
IBM Software Labs
next prev parent reply other threads:[~2006-09-18 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 1:37 [patch 0/5]-Containers: Introduction Rohit Seth
2006-09-18 13:27 ` [ckrm-tech] " Balbir Singh
2006-09-18 16:06 ` Rohit Seth
2006-09-18 18:08 ` Balbir Singh [this message]
2006-09-18 21:08 ` Badari Pulavarty
2006-09-18 22:42 ` Rohit Seth
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=450EE085.5000704@in.ibm.com \
--to=balbir@in.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rohitseth@google.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.