Searched hist:c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 (Results 1 – 9 of 9) sorted by relevance
/openbmc/linux/fs/ocfs2/ |
H A D | dlmglue.h | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
H A D | inode.h | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
H A D | mmap.c | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
H A D | inode.c | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
H A D | dlmglue.c | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
H A D | aops.c | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
H A D | super.c | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
H A D | file.c | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
/openbmc/linux/fs/ocfs2/cluster/ |
H A D | tcp_internal.h | diff c934a92d05b549dd2f25db72c5fc3cb9dcf1b611 Thu Oct 18 17:23:46 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: Remove data locks
The meta lock now covers both meta data and data, so this just removes the now-redundant data lock.
Combining locks saves us a round of lock mastery per inode and one less lock to ping between nodes during read/write.
We don't lose much - since meta locks were always held before a data lock (and at the same level) ordered writeout mode (the default) ensured that flushing for the meta data lock also pushed out data anyways.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|