Roadmaps
Filebench 1.5
Big changes: - Import of a file system tree - Custom variables - Non-interactive runs
Others are reductions only! - Grammer clean-up - Clean-up & reductions - Performance improvements
Filebench Future
- Testing platform
Various
To discuss with George
- Separate commit for every logical (even small) change
- Kernel coding conventions. E.g., (avd == NULL) => !avd
int function()
commits should pass checkpatch.pl
- No code that is not used by anything. Should be used by at least something.
- configure.ac Makefile.am changes cause changes in configure/Makefile and others. Use CentOS 6.4 with specific autotools versions. Have a git-verify hook for this?
- No new grammar rules, only reductions in release 1.5. I would really like to avoid addition to grammar at this stage. I'm fine with import functionality though.
- mmap functionality
- Versioning 1.5 or 1.5.0?... Workload files versions
- I'm not a big fan of large comments. Code should explain itself. But, where necessary, the comments should present.
- Testing on varilous platforms: set of tests - both perfomance and
functionality. Different systems. May be on ramdisk?... With many threads?
- Replace random variables by custom variables?
Specifics:
- change in avd_get_int - shouldn't that change avd_get_* every - I don't like randvar printing reintroduction (.seed, .gamma, .type) - Path changes: what if user specifies same directory?... - I like *.fb extension
Plan
- There are many useful changes from George. I don't want to change code until he has sent all of the in a proper way. - Then the plan can be that: 1) George sends all small scattered patches to me in the coming weeks. We do ping-pong 2) I meanwhile work only on the wiki & testing - When we're done with the bul of Gerge's small patches - we do regular procedure, but my freeze is over. - For now I think sending patches is the best option. Git push-pull seems to be not easy at this point.
Other things to fix
- Raw device functionality is broken - Remove boolean_t