Home
last modified time | relevance | path

Searched hist:fe1bdedc6c16adedc6fd3636185ea91596b1d6eb (Results 1 – 5 of 5) sorted by relevance

/linux/fs/gfs2/
H A Dglock.hdiff fe1bdedc6c16adedc6fd3636185ea91596b1d6eb Tue Apr 18 16:09:15 CEST 2006 Steven Whitehouse <swhiteho@redhat.com> [GFS2] Use vmalloc() in dir code

When allocating memory to sort directory entries, use vmalloc()
rather than kmalloc() since for larger directories, the required
size can easily be graeter than the 128k maximum of kmalloc().

Also adding the first steps towards getting the AOP_TRUNCATED_PAGE
return code get in the glock code by flagging all places where we
request a glock and we are holding a page lock.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
H A Ddir.cdiff fe1bdedc6c16adedc6fd3636185ea91596b1d6eb Tue Apr 18 16:09:15 CEST 2006 Steven Whitehouse <swhiteho@redhat.com> [GFS2] Use vmalloc() in dir code

When allocating memory to sort directory entries, use vmalloc()
rather than kmalloc() since for larger directories, the required
size can easily be graeter than the 128k maximum of kmalloc().

Also adding the first steps towards getting the AOP_TRUNCATED_PAGE
return code get in the glock code by flagging all places where we
request a glock and we are holding a page lock.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
H A Dmeta_io.cdiff fe1bdedc6c16adedc6fd3636185ea91596b1d6eb Tue Apr 18 16:09:15 CEST 2006 Steven Whitehouse <swhiteho@redhat.com> [GFS2] Use vmalloc() in dir code

When allocating memory to sort directory entries, use vmalloc()
rather than kmalloc() since for larger directories, the required
size can easily be graeter than the 128k maximum of kmalloc().

Also adding the first steps towards getting the AOP_TRUNCATED_PAGE
return code get in the glock code by flagging all places where we
request a glock and we are holding a page lock.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
H A Dincore.hdiff fe1bdedc6c16adedc6fd3636185ea91596b1d6eb Tue Apr 18 16:09:15 CEST 2006 Steven Whitehouse <swhiteho@redhat.com> [GFS2] Use vmalloc() in dir code

When allocating memory to sort directory entries, use vmalloc()
rather than kmalloc() since for larger directories, the required
size can easily be graeter than the 128k maximum of kmalloc().

Also adding the first steps towards getting the AOP_TRUNCATED_PAGE
return code get in the glock code by flagging all places where we
request a glock and we are holding a page lock.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
H A Dglock.cdiff fe1bdedc6c16adedc6fd3636185ea91596b1d6eb Tue Apr 18 16:09:15 CEST 2006 Steven Whitehouse <swhiteho@redhat.com> [GFS2] Use vmalloc() in dir code

When allocating memory to sort directory entries, use vmalloc()
rather than kmalloc() since for larger directories, the required
size can easily be graeter than the 128k maximum of kmalloc().

Also adding the first steps towards getting the AOP_TRUNCATED_PAGE
return code get in the glock code by flagging all places where we
request a glock and we are holding a page lock.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>