"5de0c0e5" (history) in projects: dragonfly

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"5 de0c0e5" (Results 1 – 9 of 9) sorted by relevance

/dragonfly/sys/vfs/hammer/
H A D	hammer_mount.h	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer_btree.h	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer_transaction.c	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer_ioctl.h	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer_subs.c	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer_disk.h	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer_vfsops.c	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer_inode.c	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.
H A D	hammer.h	5de0c0e5 Mon Jun 23 21:42:48 GMT 2008 Matthew Dillon <dillon@dragonflybsd.org> HAMMER 58A/Many: Mirroring support part 1 * Implement mastership domains for transaction ids to support multi-master mirroring and implement mastership selection at mount time. Mastership domains work by having the low 4 bits of the transaction id specify the mastership id (0-15). This allows the mirroring code to distinguish between changes originating on a particular node and changes mirrored from another node. This also ensures that filesystem objects can be created on the mirrors in parallel without resulting in conflicitng object ids. * Eliminate time-based TID generation. Just increment the TID as appropriate. NOTE: Portions of this change may be reverted at a later time depending on how the mirroring implementation proceeds. * Minor code cleanups.