Searched hist:"354 a3399dc6f7e556d04e1c731cd50e08eeb44bd" (Results 1 – 6 of 6) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | node.h | diff 354a3399dc6f7e556d04e1c731cd50e08eeb44bd Thu Jun 13 18:52:35 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> f2fs: recover wrong pino after checkpoint during fsync
If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
|
| H A D | dir.c | diff 354a3399dc6f7e556d04e1c731cd50e08eeb44bd Thu Jun 13 18:52:35 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> f2fs: recover wrong pino after checkpoint during fsync
If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
|
| H A D | namei.c | diff 354a3399dc6f7e556d04e1c731cd50e08eeb44bd Thu Jun 13 18:52:35 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> f2fs: recover wrong pino after checkpoint during fsync
If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
|
| H A D | segment.c | diff 354a3399dc6f7e556d04e1c731cd50e08eeb44bd Thu Jun 13 18:52:35 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> f2fs: recover wrong pino after checkpoint during fsync
If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
|
| H A D | file.c | diff 354a3399dc6f7e556d04e1c731cd50e08eeb44bd Thu Jun 13 18:52:35 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> f2fs: recover wrong pino after checkpoint during fsync
If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
|
| H A D | f2fs.h | diff 354a3399dc6f7e556d04e1c731cd50e08eeb44bd Thu Jun 13 18:52:35 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> f2fs: recover wrong pino after checkpoint during fsync
If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
|