haiwan
/
ck
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '85709d0bc2'
${ noResults }
ck/regressions/ck_epoch/validate/Makefile

43 lines
1.7 KiB
Raw Normal View History Unescape

build/regressions: Add CORES option, add "check" target. The check target will attempt to run the unit tests with some sane defaults.
12 years ago
.PHONY: check clean distribution
ck_epoch: Remove debug output, update comments.
14 years ago
ck_epoch: Allow for forward progress in concurrent epoch sections. This work is derived directly from the work of John Esmet and Paul Khuong ({jesmet,pkhuong}@appnexus.com) and PR34.
9 years ago
OBJECTS=ck_stack ck_epoch_synchronize ck_epoch_poll ck_epoch_call \
regressions/epoch: Add new torture test. Verified with fault injection into ck_epoch_synchronize.
9 years ago
ck_epoch_section ck_epoch_section_2 torture
regressions/ck_epoch: Multiple writers for synchronize unit test.
12 years ago
HALF=`expr $(CORES) / 2`
ck_epoch: Remove debug output, update comments.
14 years ago
all: $(OBJECTS)
build/regressions: Add CORES option, add "check" target. The check target will attempt to run the unit tests with some sane defaults.
12 years ago
check: all
ck_epoch: Major redesign and rewrite. I had the pleasure of spending a significant amount of time at the most recent LPC with Mathieu Desnoyers and Paul McKenney. In discussing RCU semantics in relation to epoch reclamation, it was argued that epoch reclamation is a specialisation of RCU (rather than a generalization). In light of this discussion, I thought it would make more sense to not expose write-side synchronization semantics aside from ck_epoch_call (similar to RCU call), ck_epoch_poll (identical to tick), ck_epoch_barrier and ck_epoch_synchronization (similar to ck_epoch_synchronization). Writers will now longer have to use write-side epoch sections but can instead rely on epoch_barrier/synchronization for blocking semantics and ck_epoch_poll for old tick semantics. One advantage of this is we can avoid write-side recursion for certain workloads. Additionally, for infrequent writes, epoch_barrier and epoch_synchronization both allow for blocking semantics to be used so you don't have to pay the cost of epoch_entry for non-blocking dispatch. Example usage: e = stack_pop(mystack); ck_epoch_synchronize(...); free(e); read_begin and read_end has been replaced with ck_epoch_begin and ck_epoch_end. If multiple writers need SMR guarantees, then they can also use ck_epoch_begin and ck_epoch_end. Any dispatch in presence of multiple writers should be done with-in an epoch section (for now). There are some follow-up commits to come.
12 years ago
./ck_stack $(CORES) 1
regressions/ck_epoch: Multiple writers for synchronize unit test.
12 years ago
./ck_epoch_synchronize $(HALF) $(HALF) 1
regressions/ck_epoch: Update check target. Makefile was ignored due to bogus gitignore entry.
12 years ago
./ck_epoch_poll $(CORES) 1 1
ck_epoch: Allow for forward progress in concurrent epoch sections. This work is derived directly from the work of John Esmet and Paul Khuong ({jesmet,pkhuong}@appnexus.com) and PR34.
9 years ago
./ck_epoch_section
regressions/epoch: Additional coverage for epoch sections.
9 years ago
./ck_epoch_section_2 $(HALF) $(HALF) 1
regressions/epoch: Add new torture test. Verified with fault injection into ck_epoch_synchronize.
9 years ago
./torture $(HALF) $(HALF) 1
build/regressions: Add CORES option, add "check" target. The check target will attempt to run the unit tests with some sane defaults.
12 years ago
ck_epoch: Major redesign and rewrite. I had the pleasure of spending a significant amount of time at the most recent LPC with Mathieu Desnoyers and Paul McKenney. In discussing RCU semantics in relation to epoch reclamation, it was argued that epoch reclamation is a specialisation of RCU (rather than a generalization). In light of this discussion, I thought it would make more sense to not expose write-side synchronization semantics aside from ck_epoch_call (similar to RCU call), ck_epoch_poll (identical to tick), ck_epoch_barrier and ck_epoch_synchronization (similar to ck_epoch_synchronization). Writers will now longer have to use write-side epoch sections but can instead rely on epoch_barrier/synchronization for blocking semantics and ck_epoch_poll for old tick semantics. One advantage of this is we can avoid write-side recursion for certain workloads. Additionally, for infrequent writes, epoch_barrier and epoch_synchronization both allow for blocking semantics to be used so you don't have to pay the cost of epoch_entry for non-blocking dispatch. Example usage: e = stack_pop(mystack); ck_epoch_synchronize(...); free(e); read_begin and read_end has been replaced with ck_epoch_begin and ck_epoch_end. If multiple writers need SMR guarantees, then they can also use ck_epoch_begin and ck_epoch_end. Any dispatch in presence of multiple writers should be done with-in an epoch section (for now). There are some follow-up commits to come.
12 years ago
ck_epoch_synchronize: ck_epoch_synchronize.c ../../../include/ck_stack.h ../../../include/ck_epoch.h ../../../src/ck_epoch.c
$(CC) $(CFLAGS) -o ck_epoch_synchronize ck_epoch_synchronize.c ../../../src/ck_epoch.c
ck_epoch_poll: ck_epoch_poll.c ../../../include/ck_stack.h ../../../include/ck_epoch.h ../../../src/ck_epoch.c
$(CC) $(CFLAGS) -o ck_epoch_poll ck_epoch_poll.c ../../../src/ck_epoch.c
ck_epoch: Collect from previous instance of epoch. Add torture test. This typo lead to incorrect results. Added a read-mostly torture test (follow on work is volatile interface for stack).
14 years ago
regressions/epoch: Add new torture test. Verified with fault injection into ck_epoch_synchronize.
9 years ago
torture: torture.c ../../../include/ck_epoch.h ../../../src/ck_epoch.c
$(CC) $(CFLAGS) -o torture torture.c ../../../src/ck_epoch.c
regressions/epoch: Additional coverage for epoch sections.
9 years ago
ck_epoch_section: ck_epoch_section.c ../../../include/ck_epoch.h ../../../src/ck_epoch.c
ck_epoch: Allow for forward progress in concurrent epoch sections. This work is derived directly from the work of John Esmet and Paul Khuong ({jesmet,pkhuong}@appnexus.com) and PR34.
9 years ago
$(CC) $(CFLAGS) -o ck_epoch_section ck_epoch_section.c ../../../src/ck_epoch.c
regressions/epoch: Additional coverage for epoch sections.
9 years ago
ck_epoch_section_2: ck_epoch_section_2.c ../../../include/ck_epoch.h ../../../src/ck_epoch.c
$(CC) $(CFLAGS) -o ck_epoch_section_2 ck_epoch_section_2.c ../../../src/ck_epoch.c
ck_epoch: Allow for deferral from callbacks. This makes things much easier in cases where deferral is mixed with other reclamation mechanisms such as reference counters.
10 years ago
ck_epoch_call: ck_epoch_call.c ../../../include/ck_stack.h ../../../include/ck_epoch.h ../../../src/ck_epoch.c
$(CC) $(CFLAGS) -o ck_epoch_call ck_epoch_call.c ../../../src/ck_epoch.c
ck_epoch: Support per-object destructors. This increases epoch per-object overhead to 16 bytes.
13 years ago
ck_stack: ck_stack.c ../../../include/ck_stack.h ../../../include/ck_epoch.h ../../../src/ck_epoch.c
$(CC) $(CFLAGS) -o ck_stack ck_stack.c ../../../src/ck_epoch.c
ck_epoch: Remove debug output, update comments.
14 years ago
clean:
regressions: Make clean and gettimeofday fixes.
12 years ago
rm -rf *~ *.o $(OBJECTS) *.dSYM *.exe
ck_epoch: Remove debug output, update comments.
14 years ago
include ../../../build/regressions.build
regressions/ck_epoch: Drop debug flags.
12 years ago
CFLAGS+=$(PTHREAD_CFLAGS) -D_GNU_SOURCE