Am 28.06.2016 um 16:20 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 28.06.2016 um 13:35 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 28.06.2016 um 12:57 schrieb Dr. David Alan Gilbert:
* Paolo Bonzini (pbonz...@redhat.com) wrote:
On 28/06
* Peter Lieven (p...@kamp.de) wrote:
> Am 28.06.2016 um 13:35 schrieb Dr. David Alan Gilbert:
> > * Peter Lieven (p...@kamp.de) wrote:
> > > Am 28.06.2016 um 12:57 schrieb Dr. David Alan Gilbert:
> > > > * Paolo Bonzini (pbonz...@redhat.com) wrote:
> > > > > On 28/06/2016 11:01, Peter Lieven wrote:
Am 28.06.2016 um 13:35 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 28.06.2016 um 12:57 schrieb Dr. David Alan Gilbert:
* Paolo Bonzini (pbonz...@redhat.com) wrote:
On 28/06/2016 11:01, Peter Lieven wrote:
evaluation with the recently introduced maximum stack size m
* Peter Lieven (p...@kamp.de) wrote:
> Am 28.06.2016 um 12:57 schrieb Dr. David Alan Gilbert:
> > * Paolo Bonzini (pbonz...@redhat.com) wrote:
> > >
> > > On 28/06/2016 11:01, Peter Lieven wrote:
> > > > evaluation with the recently introduced maximum stack size monitoring
> > > > revealed
> > >
- Original Message -
> From: "Peter Lieven"
> To: "Paolo Bonzini" , qemu-devel@nongnu.org
> Cc: kw...@redhat.com, "peter maydell" ,
> m...@redhat.com, dgilb...@redhat.com,
> mre...@redhat.com, kra...@redhat.com
> Sent: Tuesday, June 28, 2016 1:13:26 PM
> Subject: Re: [PATCH 03/15] corou
Am 28.06.2016 um 12:57 schrieb Dr. David Alan Gilbert:
* Paolo Bonzini (pbonz...@redhat.com) wrote:
On 28/06/2016 11:01, Peter Lieven wrote:
evaluation with the recently introduced maximum stack size monitoring revealed
that the actual used stack size was never above 4kB so allocating 1MB stac
Am 28.06.2016 um 12:54 schrieb Paolo Bonzini:
On 28/06/2016 11:01, Peter Lieven wrote:
evaluation with the recently introduced maximum stack size monitoring revealed
that the actual used stack size was never above 4kB so allocating 1MB stack
for each coroutine is a lot of wasted memory. So redu
* Paolo Bonzini (pbonz...@redhat.com) wrote:
>
>
> On 28/06/2016 11:01, Peter Lieven wrote:
> > evaluation with the recently introduced maximum stack size monitoring
> > revealed
> > that the actual used stack size was never above 4kB so allocating 1MB stack
> > for each coroutine is a lot of wa
On 28/06/2016 11:01, Peter Lieven wrote:
> evaluation with the recently introduced maximum stack size monitoring revealed
> that the actual used stack size was never above 4kB so allocating 1MB stack
> for each coroutine is a lot of wasted memory. So reduce the stack size to
> 64kB which should s
evaluation with the recently introduced maximum stack size monitoring revealed
that the actual used stack size was never above 4kB so allocating 1MB stack
for each coroutine is a lot of wasted memory. So reduce the stack size to
64kB which should still give enough head room.
Signed-off-by: Peter L
10 matches
Mail list logo
