From: Jim Fehlig <jfehlig@novell.com>
To: Patrick Colp <pjcolp@cs.ubc.ca>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: help with xenstored 'hang'
Date: Thu, 01 Jul 2010 17:03:24 -0600 [thread overview]
Message-ID: <4C2D1EBC.4060105@novell.com> (raw)
In-Reply-To: <AANLkTimjPyAuYdLmdypJAzPzemn93SUJi6fH8ITZcXJ4@mail.gmail.com>
Patrick Colp wrote:
> On 1 July 2010 14:30, Jim Fehlig <jfehlig@novell.com> wrote:
>
>> Patrick Colp wrote:
>>
>>> I was recently struggling with what sounds like a not-too-dissimilar
>>> problem while working with a disaggregated version of xenstore. The
>>> ultimate solution for me was to disable pthreads in xenstore/libxs. I
>>> just commented out the following line in tools/xenstore/Makefile:
>>>
>>> xs.opic: CFLAGS += -DUSE_PTHREAD
>>>
>>> After I removed that line and rebuilt and installed xenstore, it
>>> worked just fine. I would be curious to know if this also solves your
>>> problem.
>>>
>>>
>> After more thought, this seems like it could cause problems in xend,
>> which is multi-threaded. This change essentially make the xenstore
>> client library thread-unsafe correct?
>>
>
> I don't think so. I think it just makes the xenstore library single
> threaded.
Right. But AFAICT, multiple threads in xend could use the single
xs_handle, allowing these threads to write to the handle's fd
simultaneously. With the pthreads impl, these threads must acquire the
handle's req_mutex before writing.
> In my case, I was using a single threaded application and
> still ran into this problem, as the xenstore library seems to have
> multiple threads.
It spawns one reader thread only. Requests and responses are handled on
the caller's thread of control.
Regards,
Jim
prev parent reply other threads:[~2010-07-01 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 22:15 help with xenstored 'hang' Jim Fehlig
2010-06-30 23:17 ` Patrick Colp
2010-06-30 23:31 ` Jim Fehlig
2010-07-01 21:30 ` Jim Fehlig
2010-07-01 22:33 ` Patrick Colp
2010-07-01 23:03 ` Jim Fehlig [this message]
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=4C2D1EBC.4060105@novell.com \
--to=jfehlig@novell.com \
--cc=pjcolp@cs.ubc.ca \
--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.