From: Gerd Knorr <kraxel@suse.de>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: "xm save" trouble -- deadlock?
Date: Wed, 02 Nov 2005 12:24:59 +0100 [thread overview]
Message-ID: <4368A20B.2090106@suse.de> (raw)
In-Reply-To: <20051102100429.GA408@leeni.uk.xensource.com>
> I've done a threaded fix already. You're welcome to have a go at doing it
> without a thread if you want, but I think it'll be messy.
Looks like, yes. Mixing the high-level buffered file I/O together with
select() (and non-blocking fd's) usually doesn't work out very well.
Going down using os.read() instead likely makes the code more complex
than using one thread per file descriptor ...
cheers,
Gerd
next prev parent reply other threads:[~2005-11-02 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 16:43 "xm save" trouble -- deadlock? Gerd Knorr
2005-11-01 17:15 ` Gerd Knorr
2005-11-01 18:54 ` Ewan Mellor
2005-11-02 9:25 ` Gerd Knorr
2005-11-02 10:04 ` Ewan Mellor
2005-11-02 11:24 ` Gerd Knorr [this message]
2005-11-02 15:35 ` Gerd Knorr
2005-11-02 15:41 ` Ewan Mellor
2005-11-02 17:23 ` Gerd Knorr
2005-11-01 18:58 ` Ewan Mellor
2005-11-02 11:34 ` Gerd Knorr
2005-11-02 18:28 ` Kip Macy
2005-11-03 8:53 ` Gerd Knorr
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=4368A20B.2090106@suse.de \
--to=kraxel@suse.de \
--cc=ewan@xensource.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.