From: Ewan Mellor <Ewan.Mellor@ntlworld.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/2] Change xs_read_watch interfaces to support variable arguments
Date: Tue, 4 Oct 2005 07:55:36 +0100 [thread overview]
Message-ID: <20051004065536.GA4104@linford.intra> (raw)
In-Reply-To: <4342087F.5010505@us.ibm.com>
On Mon, Oct 03, 2005 at 11:43:43PM -0500, Anthony Liguori wrote:
> The following set of changes modify the read_watch interface in
> userspace and in the kernel to support variable arguments. This is in
> preparation for adding domid to @{introduce,release}Domain watches.
> This will allow backends to automatically reap on domain destruction
> which should eliminate a large number of the zombie problems we're
> having on domain destruction since Xend no longer plays a role in
> freeing that memory.
Hi Anthony,
What you've done in your patch stands as a sensible thing on its own, I think,
so I'm not objecting to that, but I am interested in why you think it will
help with the zombies. On domain destruction, xend is _supposed_ to remove
all the relevant entries of the store, and the backend drivers are _supposed_
to notice this and close themselves down. If you have evidence that either of
those things aren't happening, then we should regard that as a bug,
independent of your patch. Have you seen that happening?
Ewan.
next prev parent reply other threads:[~2005-10-04 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 4:43 [PATCH 0/2] Change xs_read_watch interfaces to support variable arguments Anthony Liguori
2005-10-04 4:48 ` Anthony Liguori
2005-10-04 6:55 ` Ewan Mellor [this message]
2005-10-04 14:34 ` Anthony Liguori
2005-10-04 14:51 ` Ewan Mellor
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=20051004065536.GA4104@linford.intra \
--to=ewan.mellor@ntlworld.com \
--cc=xen-devel@lists.xensource.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.