summaryrefslogtreecommitdiff
path: root/BS
AgeCommit message (Collapse)AuthorLines
2024-03-08BS: avoid double freeBirte Kristina Friesel-0/+2
2024-03-08BS: handle alloc/load/free overhead as parameters; vary them for fgbs24aBirte Kristina Friesel-4/+11
2024-02-28more run-fgbs24aBirte Kristina Friesel-0/+28
2023-12-01BS: add overhead measurementsBirte Kristina Friesel-46/+144
2023-08-03run-opti: PrIM always uses four threads for CPU baselineBirte Kristina Friesel-2/+2
2023-07-24BS: adjust #DPUs for tinosBirte Friesel-2/+3
2023-07-24BFS, BS: remove duplicate configurationsBirte Friesel-2/+2
2023-07-06run-strong-full: add 2544 DPUs (maximum possible on tinos @ UOS)Birte Friesel-1/+2
2023-06-01BS: updates and commentsDaniel Friesel-18/+33
2023-05-31BS: add 256 and 512 DPUs to benchmarksDaniel Friesel-2/+4
2023-05-30BS: switch to new dfatool format; add -O and reproduction scriptsDaniel Friesel-15/+92
2023-05-25port BS NMC to dfatoolDaniel Friesel-45/+89
2023-05-25port BS CPU to dfatoolDaniel Friesel-6/+70
2021-12-23bs_refactor: Remove printf for loggingYun-Ze Li-8/+2
Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-23bs_refactor: Remove redundant linesYun-Ze Li-7/+4
This commit reduce redundant lines for calculating `current_mram_block_addrA`. Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-23bs_bug_fix: Modify boundary case handlings in BSYun-Ze Li-41/+38
Current boundary case handling may discard some numbers obliged to be compared with `searching_for`, which in my opinion can result in false positives (BS fails to identify the number which is indeed in the input array). This commit changed the boundary check condition to `if(current_mram_block_addr_A < start_mram_block_addr_A + BLOCK_SIZE)`, where the expression returns true if and only if the length of the range [start_mram_block_addr_A, end_mram_block_addr_A) has become smaller than 2*BLOCK_SIZE. When this happens, we can then finalize the BS result by checking if `searching_for` exists within [start_mram_block_addr_A, end_mram_block_addr_A) without overlooking any number that should be checked. Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-23bs_bug_fix: Make MRAM reads 8-byte alignedYun-Ze Li-0/+15
Current implementation does not guarantee that `current_mram_block_addr_A` is 8-byte aligned before using it as the start address of `mram_read`s. This commit makes `current_mram_block_addr_A` 8-byte aligned whenever we try to use it for a MRAM read by `current_mram_block_addr_A &= WORD_MASK`, which will clear the unaligned bytes. Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-06-16PrIM -- first commitJuan Gomez Luna-0/+1007