From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: ltp-list <ltp-list@lists.sf.net>,
Oren Laadan <orenl@cs.columbia.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
matthltc <matthltc@linux.vnet.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Serge Hallyn <serue@linux.vnet.ibm.com>,
sukadev <sukadev@linux.vnet.ibm.com>
Subject: Re: [LTP] [RFC v13][PATCH 00/14] Kernel based checkpoint/restart
Date: Tue, 23 Jun 2009 10:02:30 -0500 [thread overview]
Message-ID: <20090623150230.GA20383@us.ibm.com> (raw)
In-Reply-To: <1245768524.4860.60.camel@subratamodak.linux.ibm.com>
Quoting Subrata Modak (subrata@linux.vnet.ibm.com):
> On Wed, 2009-03-18 at 19:33 +0530, Subrata Modak wrote:
> > Thanks Serge.
> >
> > On Wed, 2009-03-18 at 08:39 -0500, Serge E. Hallyn wrote:
> > > Quoting Subrata Modak (subrata@linux.vnet.ibm.com):
> > > > Serge,
> > > >
> > > > Did i talk to you regarding these tests in our OLS 2008 meeting ? I do
> > > > not remember exactly, but, when i saw this posting, i thought may be
> > > > there was some conversation.
> > >
> > > I'm not sure. However no patches are in -mm or linux-next yet.
> > >
> > > I'm not yet certain what the test methodology will be. Some for
> > > instance feel that the best way to test c/r is to just run ltp
> > > inside a container and continuously c/r it. Of course, that
> > > isn't very useful when c/r support is not yet sufficient to
> > > accomplish that. So at the moment we do have sets of programs
> > > specifically written to be checkpointable.
> > >
> > > For instance I have a program and script which continuously
> > > runs, updates state, writes to a file, checkpoints, kills,
> > > and restarts. That sort of thing should make a nice testcase.
> > > Oren maintains a git tree with checkpointable programs at
> > > git://git.ncl.cs.columbia.edu/pub/git/user-cr.git .
> > >
> > > So definately let's talk again after patches hit mainline. I'll
> > > whip up some testcases based on existing code.
>
> Serge,
>
> Do we have this in 2.6.30 ?
Let me check!
Heh, just kidding. Nope.
-serge
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-06-23 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1233076092-8660-1-git-send-email-orenl@cs.columbia.edu>
[not found] ` <bb33bcf20903160526v56f16a82m9192770e228016b1@mail.gmail.com>
[not found] ` <1237365510.5381.34.camel@subratamodak.linux.ibm.com>
[not found] ` <20090318133943.GA22636@us.ibm.com>
[not found] ` <1237385013.5381.58.camel@subratamodak.linux.ibm.com>
2009-06-23 14:48 ` [LTP] [RFC v13][PATCH 00/14] Kernel based checkpoint/restart Subrata Modak
2009-06-23 15:02 ` Serge E. Hallyn [this message]
2009-06-25 9:10 ` Subrata Modak
2009-09-13 13:16 ` Subrata Modak
2009-09-13 20:06 ` Serge E. Hallyn
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=20090623150230.GA20383@us.ibm.com \
--to=serue@us.ibm.com \
--cc=hpa@zytor.com \
--cc=ltp-list@lists.sf.net \
--cc=matthltc@linux.vnet.ibm.com \
--cc=orenl@cs.columbia.edu \
--cc=serue@linux.vnet.ibm.com \
--cc=subrata@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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