1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/__brch__HW__generic_x86_64_MC	Sat Feb 11 21:43:43 2012 -0800
     1.3 @@ -0,0 +1,33 @@
     1.4 +A HW branch for:
     1.5 +
     1.6 +generic MultiCore  x86 64bit instructions set
     1.7 +
     1.8 +This branch shouldn't be used, except as a lazy fall-back.  Instead, try out other branches tuned to specific hardware platforms to find the one that performs best on your machine.  Use the "exe_time_vs_task_size" project to generate curves of overhead, and compare result from various branches.
     1.9 +
    1.10 +Note, if this branch is used, then vms_defs.h file has to be updated with the number of cores in your machine
    1.11 +
    1.12 +========  Background on branch naming  =========
    1.13 +
    1.14 +There are two kinds of branchs: ones used to develop features, and ones tuned to particular hardware.  A given HW branch may combine features from several feature-branches, picking and choosing among them.
    1.15 +
    1.16 +After Feb 2012, branches are named by the scheme:
    1.17 +
    1.18 +feat__<feat_descr>__<HW_feat_dev_on>
    1.19 +
    1.20 +HW__<desc_of_HW_brch_tuned_for>
    1.21 +
    1.22 +where <HW_feat_dev_on> and <desc_of_HW_brch_tuned_for> follow the pattern:
    1.23 +
    1.24 +<num_socket> x <num_cores>_<Manuf>_<special_features>
    1.25 +
    1.26 +Examples:
    1.27 +
    1.28 +feat__exp_array_malloc
    1.29 +
    1.30 +feat__rand_backoff__4x10_Intel_WestmereEx
    1.31 +
    1.32 +HW__1x4_Intel_SandyBridge
    1.33 +
    1.34 +HW__4x10_Intel_WestmereEx
    1.35 +
    1.36 +HW__1x4_AMD_mobile