# HG changeset patch
# User Me@portablequad
# Date 1329025423 28800
# Node ID 37b06118011926b625a6395a785ba014e7d2253c
# Parent  7cff4e13d5c423299ec9e8ea2d687a90f75f8a50
Created HW_generic_x86_64_MC  branch (see __brch__* for expl)

diff -r 7cff4e13d5c4 -r 37b061180119 __brch__HW__generic_x86_64_MC
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/__brch__HW__generic_x86_64_MC	Sat Feb 11 21:43:43 2012 -0800
@@ -0,0 +1,33 @@
+A HW branch for:
+
+generic MultiCore  x86 64bit instructions set
+
+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.
+
+Note, if this branch is used, then vms_defs.h file has to be updated with the number of cores in your machine
+
+========  Background on branch naming  =========
+
+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.
+
+After Feb 2012, branches are named by the scheme:
+
+feat__<feat_descr>__<HW_feat_dev_on>
+
+HW__<desc_of_HW_brch_tuned_for>
+
+where <HW_feat_dev_on> and <desc_of_HW_brch_tuned_for> follow the pattern:
+
+<num_socket> x <num_cores>_<Manuf>_<special_features>
+
+Examples:
+
+feat__exp_array_malloc
+
+feat__rand_backoff__4x10_Intel_WestmereEx
+
+HW__1x4_Intel_SandyBridge
+
+HW__4x10_Intel_WestmereEx
+
+HW__1x4_AMD_mobile