[lkml]   [2004]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Non-GPL export of invalidate_mmap_range
On Wed, Feb 18, 2004 at 09:10:35PM +0000, Christoph Hellwig wrote:
> On Wed, Feb 18, 2004 at 06:00:21AM -0800, Paul E. McKenney wrote:
> > There is a small shim layer required, but the bulk of the code
> > implementing GPFS is common between AIX and Linux. It was on AIX
> > first by quite a few years.
> Small glue layer? Unfortunately ibm took it off the website, but
> the thing is damn huge.

Perhaps it is huge, but it is a small fraction of the GPFS kernel

> > > it only uses "core unix" apis ?
> >
> > If they are made available, yes. That is the point of this patch,
> > after all. ;-)
> No, that's wrong. It patches the syscall table and plays evilish
> tricks with lowlevel MM code.

The sys_call_table stuff was under #ifdef, and was intended for
use by a research project that was later put out of its misery.
This stuff has since been removed from the source tree.

As to the evilish tricks with lowlevel MM code, the whole point
of the mmap_invalidate_range() patch is to be able to rid GPFS
of exactly these evilish tricks.

> > > It doesn't require knowledge of deep and changing internals ? *buzz*
> >
> > That is indeed the idea.
> The one on the ibm website a little ago did. You're free to upload
> a new one that clearly doesn't need all this, but..

Again, the point of the mmap_invalidate_range() patch is to be able
to do precisely this.

Thanx, Paul
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:01    [W:0.095 / U:2.536 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site