Searched hist:a6591715 (Results 1 – 6 of 6) sorted by relevance
/openbmc/linux/fs/btrfs/ |
H A D | file-item.c | a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers
The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory.
The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex.
This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code.
Signed-off-by: Chris Mason <chris.mason@oracle.com> a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory. The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex. This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code. Signed-off-by: Chris Mason <chris.mason@oracle.com>
|
H A D | extent_io.h | a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers
The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory.
The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex.
This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code.
Signed-off-by: Chris Mason <chris.mason@oracle.com> a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory. The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex. This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code. Signed-off-by: Chris Mason <chris.mason@oracle.com>
|
H A D | ctree.c | a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers
The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory.
The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex.
This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code.
Signed-off-by: Chris Mason <chris.mason@oracle.com> a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory. The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex. This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code. Signed-off-by: Chris Mason <chris.mason@oracle.com>
|
H A D | extent_io.c | a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers
The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory.
The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex.
This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code.
Signed-off-by: Chris Mason <chris.mason@oracle.com> a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory. The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex. This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code. Signed-off-by: Chris Mason <chris.mason@oracle.com>
|
H A D | disk-io.c | a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers
The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory.
The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex.
This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code.
Signed-off-by: Chris Mason <chris.mason@oracle.com> a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory. The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex. This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code. Signed-off-by: Chris Mason <chris.mason@oracle.com>
|
H A D | inode.c | a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers
The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory.
The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex.
This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code.
Signed-off-by: Chris Mason <chris.mason@oracle.com> a6591715 Tue Jul 19 11:04:14 CDT 2011 Chris Mason <chris.mason@oracle.com> Btrfs: stop using highmem for extent_buffers The extent_buffers have a very complex interface where we use HIGHMEM for metadata and try to cache a kmap mapping to access the memory. The next commit adds reader/writer locks, and concurrent use of this kmap cache would make it even more complex. This commit drops the ability to use HIGHMEM with extent buffers, and rips out all of the related code. Signed-off-by: Chris Mason <chris.mason@oracle.com>
|