Home
last modified time | relevance | path

Searched hist:"254 db57f9b12daba841a4d91ddb9a8161e9c74ba" (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/fs/gfs2/
H A Dlog.cdiff 254db57f9b12daba841a4d91ddb9a8161e9c74ba Fri Sep 26 04:23:22 CDT 2008 Steven Whitehouse <swhiteho@redhat.com> GFS2: Support for I/O barriers

This patch adds barrier support to GFS2. There is not a lot of change
really... we just add the barrier flag when we write journal header
blocks. If the underlying device refuses to support them, we fall back
to the previous way of doing things (wait for the I/O and hope) since
there is nothing else we can do. There is no user configuration,
barriers will always be on unless the device refuses to support them.
This seems a reasonable solution to me since this is a correctness
issue.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
H A Dincore.hdiff 254db57f9b12daba841a4d91ddb9a8161e9c74ba Fri Sep 26 04:23:22 CDT 2008 Steven Whitehouse <swhiteho@redhat.com> GFS2: Support for I/O barriers

This patch adds barrier support to GFS2. There is not a lot of change
really... we just add the barrier flag when we write journal header
blocks. If the underlying device refuses to support them, we fall back
to the previous way of doing things (wait for the I/O and hope) since
there is nothing else we can do. There is no user configuration,
barriers will always be on unless the device refuses to support them.
This seems a reasonable solution to me since this is a correctness
issue.

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