Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

Wei Liu writes ("Re: [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread"): > On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote: > > Of course, the alternative is to bump it to another arbitrary value, but the > > requirements may change depending on the

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On 27/09/16 11:06, Wei Liu wrote: On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote: > From: Chris Patterson > > xs_watch() creates a thread to listen to xenstore events. Currently, the > thread is created with the greater of 16K or PTHREAD_MIN_SIZE. > >

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote: > From: Chris Patterson > > xs_watch() creates a thread to listen to xenstore events. Currently, the > thread is created with the greater of 16K or PTHREAD_MIN_SIZE. > > There have been several bug

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Wed, Sep 21, 2016 at 10:07:10AM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Sep 21, 2016 at 09:50:30AM -0400, Chris Patterson wrote: > > On Wed, Sep 21, 2016 at 9:00 AM, Wei Liu wrote: > > > On Wed, Sep 21, 2016 at 08:51:07AM -0400, Konrad Rzeszutek Wilk wrote: > > >> On

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Wed, Sep 21, 2016 at 10:23:09AM -0400, Chris Patterson wrote: > On Wed, Sep 21, 2016 at 10:07 AM, Konrad Rzeszutek Wilk > wrote: > > On Wed, Sep 21, 2016 at 09:50:30AM -0400, Chris Patterson wrote: > >> On Wed, Sep 21, 2016 at 9:00 AM, Wei Liu

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Wed, Sep 21, 2016 at 10:07 AM, Konrad Rzeszutek Wilk wrote: > On Wed, Sep 21, 2016 at 09:50:30AM -0400, Chris Patterson wrote: >> On Wed, Sep 21, 2016 at 9:00 AM, Wei Liu wrote: >> > On Wed, Sep 21, 2016 at 08:51:07AM -0400, Konrad Rzeszutek Wilk

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Wed, Sep 21, 2016 at 09:50:30AM -0400, Chris Patterson wrote: > On Wed, Sep 21, 2016 at 9:00 AM, Wei Liu wrote: > > On Wed, Sep 21, 2016 at 08:51:07AM -0400, Konrad Rzeszutek Wilk wrote: > >> On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote: > >> > From:

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Wed, Sep 21, 2016 at 9:00 AM, Wei Liu wrote: > On Wed, Sep 21, 2016 at 08:51:07AM -0400, Konrad Rzeszutek Wilk wrote: >> On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote: >> > From: Chris Patterson >> > >> > xs_watch() creates a

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Wed, Sep 21, 2016 at 08:51:07AM -0400, Konrad Rzeszutek Wilk wrote: > On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote: > > From: Chris Patterson > > > > xs_watch() creates a thread to listen to xenstore events. Currently, the > > thread is created

Re: [Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote: > From: Chris Patterson > > xs_watch() creates a thread to listen to xenstore events. Currently, the > thread is created with the greater of 16K or PTHREAD_MIN_SIZE. > > There have been several bug

[Xen-devel] [RFC PATCH] xs: use system's default stack size for xs_watch's reader thread

From: Chris Patterson xs_watch() creates a thread to listen to xenstore events. Currently, the thread is created with the greater of 16K or PTHREAD_MIN_SIZE. There have been several bug reports and workarounds related to the issue where xs_watch() fails because its