On Fri, 04 May 2007 12:26:51 +0200, Peter Zijlstra <[EMAIL PROTECTED]> wrote:
>>> There is a fundamental deadlock associated with paging;
On Fri, May 04, 2007 at 12:27:16PM -0700, David Miller wrote:
>> I know you'd really like people like myself to review this work, but a
>> set of 40 patches is
On Fri, May 04, 2007 at 12:27:16PM -0700, David Miller wrote:
> From: Peter Zijlstra <[EMAIL PROTECTED]>
> Date: Fri, 04 May 2007 12:26:51 +0200
>
> > There is a fundamental deadlock associated with paging;
>
> I know you'd really like people like myself to review this work, but a
> set of 40 pat
Daniel Walker wrote:
On Fri, 2007-05-04 at 12:26 +0200, Peter Zijlstra wrote:
1) introduce the memory reserve and make the SLAB allocator play nice with it.
patches 01-10
2) add some needed infrastructure to the network code
patches 11-13
3) implement the idea outlined above
patch
David Miller wrote:
From: Peter Zijlstra <[EMAIL PROTECTED]>
Date: Fri, 04 May 2007 21:41:49 +0200
How would you prefer I present these?
How about 8 or 9 at a time? You are building infrastructure
and therefore you could post them 1 at a time for review
since each patch should be able to sta
From: Peter Zijlstra <[EMAIL PROTECTED]>
Date: Fri, 04 May 2007 21:41:49 +0200
> How would you prefer I present these?
How about 8 or 9 at a time? You are building infrastructure
and therefore you could post them 1 at a time for review
since each patch should be able to stand on it's own.
-
To u
From: "Mike Snitzer" <[EMAIL PROTECTED]>
Date: Fri, 4 May 2007 14:09:40 -0400
> These suggestions conflict in the case of a large patchset: the second
> can't be met if you honor the first (more important suggestion IMHO).
> Unless you leave something out... and I can't see the value in leaving
>
On Fri, 2007-05-04 at 12:27 -0700, David Miller wrote:
> From: Peter Zijlstra <[EMAIL PROTECTED]>
> Date: Fri, 04 May 2007 12:26:51 +0200
>
> > There is a fundamental deadlock associated with paging;
>
> I know you'd really like people like myself to review this work, but a
> set of 40 patches is
On Fri, 2007-05-04 at 14:09 -0400, Mike Snitzer wrote:
> On 5/4/07, Daniel Walker <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-05-04 at 17:38 +0200, Peter Zijlstra wrote:
> > > >
> > > > This is kind of a lot of patches all at once .. Have you release any of
> > > > these patch sets prior to this re
From: Peter Zijlstra <[EMAIL PROTECTED]>
Date: Fri, 04 May 2007 12:26:51 +0200
> There is a fundamental deadlock associated with paging;
I know you'd really like people like myself to review this work, but a
set of 40 patches is just too much to try and digest at once
especially when I have other
On 5/4/07, Daniel Walker <[EMAIL PROTECTED]> wrote:
On Fri, 2007-05-04 at 17:38 +0200, Peter Zijlstra wrote:
> >
> > This is kind of a lot of patches all at once .. Have you release any of
> > these patch sets prior to this release ?
>
> Like the -v12 suggests, this is the 12th posting of this pa
On Fri, 2007-05-04 at 17:38 +0200, Peter Zijlstra wrote:
> >
> > This is kind of a lot of patches all at once .. Have you release any of
> > these patch sets prior to this release ?
>
> Like the -v12 suggests, this is the 12th posting of this patch set.
> Some is the same, some has changed.
I c
On Fri, 2007-05-04 at 08:22 -0700, Daniel Walker wrote:
> On Fri, 2007-05-04 at 12:26 +0200, Peter Zijlstra wrote:
>
> > 1) introduce the memory reserve and make the SLAB allocator play nice with
> > it.
> >patches 01-10
> >
> > 2) add some needed infrastructure to the network code
> >pa
On Fri, 2007-05-04 at 12:26 +0200, Peter Zijlstra wrote:
> 1) introduce the memory reserve and make the SLAB allocator play nice with it.
>patches 01-10
>
> 2) add some needed infrastructure to the network code
>patches 11-13
>
> 3) implement the idea outlined above
>patches 14-20
>
13 matches
Mail list logo
