I apologize again for the long delay in responding with the requested
additional data needed to understand the performance of this patch.
The complete information is available at:
http://www.cs.utexas.edu/~porterde/kernel-patch.html#subsequent
I instrumented the kernel within simics to determine
I apologize again for the long delay in responding with the requested
additional data needed to understand the performance of this patch.
The complete information is available at:
http://www.cs.utexas.edu/~porterde/kernel-patch.html#subsequent
I instrumented the kernel within simics to determine
Thank you all for your consideration and insightful responses to my
posting. I apologize for not responding sooner---I have been under a
deadline.
It seems clear that further investigation will be needed to understand
these performance numbers better.
To summarize, I understand that the
Thank you all for your consideration and insightful responses to my
posting. I apologize for not responding sooner---I have been under a
deadline.
It seems clear that further investigation will be needed to understand
these performance numbers better.
To summarize, I understand that the
On Wednesday 07 November 2007 17:19, Andrew Morton wrote:
> > On Tue, 06 Nov 2007 05:08:07 -0500 Chris Snook <[EMAIL PROTECTED]> wrote:
> >
> > Don Porter wrote:
> > > From: Donald E. Porter <[EMAIL PROTECTED]>
> > >
> > > In the bulk page allocation/free routines in mm/page_alloc.c, the zone
> >
> On Tue, 06 Nov 2007 05:08:07 -0500 Chris Snook <[EMAIL PROTECTED]> wrote:
> Don Porter wrote:
> > From: Donald E. Porter <[EMAIL PROTECTED]>
> >
> > In the bulk page allocation/free routines in mm/page_alloc.c, the zone
> > lock is held across all iterations. For certain parallel workloads, I
Don Porter wrote:
From: Donald E. Porter <[EMAIL PROTECTED]>
In the bulk page allocation/free routines in mm/page_alloc.c, the zone
lock is held across all iterations. For certain parallel workloads, I
have found that releasing and reacquiring the lock for each iteration
yields better
Don Porter wrote:
From: Donald E. Porter [EMAIL PROTECTED]
In the bulk page allocation/free routines in mm/page_alloc.c, the zone
lock is held across all iterations. For certain parallel workloads, I
have found that releasing and reacquiring the lock for each iteration
yields better
On Tue, 06 Nov 2007 05:08:07 -0500 Chris Snook [EMAIL PROTECTED] wrote:
Don Porter wrote:
From: Donald E. Porter [EMAIL PROTECTED]
In the bulk page allocation/free routines in mm/page_alloc.c, the zone
lock is held across all iterations. For certain parallel workloads, I
have found
On Wednesday 07 November 2007 17:19, Andrew Morton wrote:
On Tue, 06 Nov 2007 05:08:07 -0500 Chris Snook [EMAIL PROTECTED] wrote:
Don Porter wrote:
From: Donald E. Porter [EMAIL PROTECTED]
In the bulk page allocation/free routines in mm/page_alloc.c, the zone
lock is held across
From: Donald E. Porter <[EMAIL PROTECTED]>
In the bulk page allocation/free routines in mm/page_alloc.c, the zone
lock is held across all iterations. For certain parallel workloads, I
have found that releasing and reacquiring the lock for each iteration
yields better performance, especially at
From: Donald E. Porter [EMAIL PROTECTED]
In the bulk page allocation/free routines in mm/page_alloc.c, the zone
lock is held across all iterations. For certain parallel workloads, I
have found that releasing and reacquiring the lock for each iteration
yields better performance, especially at
12 matches
Mail list logo
