Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [RFC][PATCH 0/6][usercr]: Rename/reorg usercr code
Date: Sun, 25 Apr 2010 16:24:33 -0400	[thread overview]
Message-ID: <4BD4A501.6070106@cs.columbia.edu> (raw)
In-Reply-To: <20100420180733.GA13874-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

Hi Suka,

Thanks for the patchset. A couple of comments:

* I prefer the header exported to users to be checkpoint.h - this
is consistent with kernel headers, and with future name of a c/r
library if we opt libcheckpoint.a

* I also prefer to leave checkpoint.c as a separate file, as is.
It may gain more functionality in the future. If the goal was to
only export a single .o file, then the solution IMHO is to instead
export a single library: libcheckpoint.a

Unless you have a strong opinion against the above, I'll go ahead
and pull patches 1-3, leave out 4-6, and update the Makefile to
create a libcheckpoint.a library.

Oren.


Sukadev Bhattiprolu wrote:
> Sukadev Bhattiprolu [sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org] wrote:
> | 
> | Change the prefix of the USERCR apis to 'cr_' and reorg the code to avoid
> | duplication and reduce code size.
> | 
> | 	[PATCH 1/6] Change API prefix to cr_
> | 	[PATCH 2/6] Remove flags parameter to cr_checkpoint()
> | 	[PATCH 3/6] Minor reorg of restart.c
> | 	[PATCH 4/6] Move checkpoint() into restart.c
> | 	[PATCH 5/6] Rename restart.c to cr_checkpoint.c
> | 	[PATCH 6/6] Rename common.h to cr_log.h
> | 
> | With this change, USERCR for now "exports" just the following two files:
> | 
> | 	cr_checkpoint.o
> | 	cr_checkpoint.h
> | 
> | But this patchset does cause some churn, let me know if you think any of it
> | is unnecessary/noise.  I have tested for now along with the patch that removes
> | most exits() from cr_restart(). If the reorg makes sense, will run all tests
> | once more and resubmit.
> 
> All tests in cr-tests pass with these two patchsets (on usercr ckpt-v20-dev
> and linux ckpt-v21-rc2).
> 
> Pls let me know if there are comments about the patchsets.
> 
> Thanks,
> 
> Sukadev
> 

  parent reply	other threads:[~2010-04-25 20:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  0:49 [RFC][PATCH 0/6][usercr]: Rename/reorg usercr code Sukadev Bhattiprolu
     [not found] ` <20100414004927.GA13012-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-14  0:52   ` [RFC][PATCH 1/6][usercr] Change API prefix to cr_ Sukadev Bhattiprolu
2010-04-14  0:52   ` [RFC][PATCH 2/6][usercr] Remove flags parameter to cr_checkpoint() Sukadev Bhattiprolu
2010-04-14  0:52   ` [RFC][PATCH 3/6][usercr] Minor reorg of restart.c Sukadev Bhattiprolu
2010-04-14  0:52   ` [RFC][PATCH 4/6][usercr] Move checkpoint() into restart.c Sukadev Bhattiprolu
2010-04-14  0:53   ` [RFC][PATCH 5/6][usercr] Rename restart.c to cr_checkpoint.c Sukadev Bhattiprolu
2010-04-14  0:53   ` [RFC][PATCH 6/6][usercr] Rename common.h to cr_log.h Sukadev Bhattiprolu
2010-04-20 18:07   ` [RFC][PATCH 0/6][usercr]: Rename/reorg usercr code Sukadev Bhattiprolu
     [not found]     ` <20100420180733.GA13874-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-25 20:24       ` Oren Laadan [this message]
     [not found]         ` <4BD4A501.6070106-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-04-26 17:16           ` Sukadev Bhattiprolu
     [not found]             ` <20100426171603.GB27542-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-26 18:46               ` Oren Laadan
2010-06-14 21:31           ` Oren Laadan

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=4BD4A501.6070106@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox