> the new fault hander made the memory manager code a lot cleaner and
> very less hacky in a lot of cases. so I'd rather merge the clean code
> than have to fight with the current code...
Note that you can probably get away with NOPFN_REFAULT etc... like I did
for the SPEs in the meantime.
the new fault hander made the memory manager code a lot cleaner and
very less hacky in a lot of cases. so I'd rather merge the clean code
than have to fight with the current code...
Note that you can probably get away with NOPFN_REFAULT etc... like I did
for the SPEs in the meantime.
On Mon, Feb 26, 2007 at 09:32:04PM -0800, Andrew Morton wrote:
> > On Tue, 27 Feb 2007 15:36:03 +1100 "Dave Airlie" <[EMAIL PROTECTED]> wrote:
> > >
> > > I've also got rid of the horrible populate API, and integrated nonlinear
> > > pages
> > > properly with the page fault path.
> > >
> > >
On Mon, Feb 26, 2007 at 09:32:04PM -0800, Andrew Morton wrote:
On Tue, 27 Feb 2007 15:36:03 +1100 Dave Airlie [EMAIL PROTECTED] wrote:
I've also got rid of the horrible populate API, and integrated nonlinear
pages
properly with the page fault path.
Downside is that this adds
> the new fault hander made the memory manager code a lot cleaner and
> very less hacky in a lot of cases. so I'd rather merge the clean code
> than have to fight with the current code...
Note that you can probably get away with NOPFN_REFAULT etc... like I did
for the SPEs in the meantime.
Ben.
On 2/27/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Tue, 27 Feb 2007 15:36:03 +1100 "Dave Airlie" <[EMAIL PROTECTED]> wrote:
> >
> > I've also got rid of the horrible populate API, and integrated nonlinear
pages
> > properly with the page fault path.
> >
> > Downside is that this adds one
> On Tue, 27 Feb 2007 15:36:03 +1100 "Dave Airlie" <[EMAIL PROTECTED]> wrote:
> >
> > I've also got rid of the horrible populate API, and integrated nonlinear
> > pages
> > properly with the page fault path.
> >
> > Downside is that this adds one more vector through which the buffered write
> >
I've also got rid of the horrible populate API, and integrated nonlinear pages
properly with the page fault path.
Downside is that this adds one more vector through which the buffered write
deadlock can occur. However this is just a very tiny one (pte being unmapped
for reclaim), compared to
I've also got rid of the horrible populate API, and integrated nonlinear pages
properly with the page fault path.
Downside is that this adds one more vector through which the buffered write
deadlock can occur. However this is just a very tiny one (pte being unmapped
for reclaim), compared to
On Tue, 27 Feb 2007 15:36:03 +1100 Dave Airlie [EMAIL PROTECTED] wrote:
I've also got rid of the horrible populate API, and integrated nonlinear
pages
properly with the page fault path.
Downside is that this adds one more vector through which the buffered write
deadlock can occur.
On 2/27/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Tue, 27 Feb 2007 15:36:03 +1100 Dave Airlie [EMAIL PROTECTED] wrote:
I've also got rid of the horrible populate API, and integrated nonlinear
pages
properly with the page fault path.
Downside is that this adds one more vector
the new fault hander made the memory manager code a lot cleaner and
very less hacky in a lot of cases. so I'd rather merge the clean code
than have to fight with the current code...
Note that you can probably get away with NOPFN_REFAULT etc... like I did
for the SPEs in the meantime.
Ben.
The following set of patches are based on current git.
These fix the fault vs invalidate and fault vs truncate_range race for
filemap_nopage mappings, plus those and fault vs truncate race for nonlinear
mappings.
These patches fix silent data corruption that we've had several people hitting
in
The following set of patches are based on current git.
These fix the fault vs invalidate and fault vs truncate_range race for
filemap_nopage mappings, plus those and fault vs truncate race for nonlinear
mappings.
These patches fix silent data corruption that we've had several people hitting
in
14 matches
Mail list logo