Linux Container Development
 help / color / mirror / Atom feed
From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	matthltc-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Subject: Re: [PATCH] Clear the objhash before completing restart, but delay free (v2)
Date: Mon, 01 Nov 2010 11:10:19 -0700	[thread overview]
Message-ID: <874oc0x6d0.fsf@localhost6.localdomain6> (raw)
In-Reply-To: <4CCEFDD4.1030308-eQaUEPhvms7ENvBUuze7eA@public.gmane.org> (Oren Laadan's message of "Mon\, 01 Nov 2010 13\:50\:12 -0400")

OL> So to be clear: is there a performance issue due to moving the
OL> cleanup - some or all - to before allowing tasks to resume ?
OL> (This is what I understood over IRC).

Not that I have been able to measure, no.

-- 
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org

  parent reply	other threads:[~2010-11-01 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 14:03 [PATCH] Clear the objhash before completing restart, but delay free (v2) Dan Smith
     [not found] ` <1287496991-18207-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-10-19 18:46   ` Matt Helsley
2010-11-01 16:24   ` Oren Laadan
     [not found]     ` <4CCEE9AD.7010105-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-11-01 17:01       ` Dan Smith
     [not found]         ` <87oca9vuyw.fsf-bi+AKbBUZKagILUCTcTcHdKyNwTtLsGr@public.gmane.org>
2010-11-01 17:50           ` Oren Laadan
     [not found]             ` <4CCEFDD4.1030308-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-11-01 18:10               ` Dan Smith [this message]
2011-02-01  0:31   ` Oren Laadan
     [not found]     ` <4D47544E.7080600-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-02-01 19:38       ` Dan Smith
     [not found]         ` <87pqrb5yvn.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2011-02-02 14:55           ` 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=874oc0x6d0.fsf@localhost6.localdomain6 \
    --to=danms-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=matthltc-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@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