Jim Huang

Analyze the impact to existing HAL and adaption layer.

Never write code in a rush. Always think of the portability, code reusability, and elegance.

Check the subject. You mentioned WP76xx platform rather than the removal of HAL!

We should follow the steps: 1. Decide the removal of HAL and validate `simu` substitute 2. Adapt existing platforms for new interface; 3. Documentation as possible; 4. Support WP76xx;

After applying [enable-rdtsc.patch](https://github.com/chenwei-tw/dcurl/files/1823210/enable-rdtsc.txt), I got the following [time-stamp](https://c9x.me/x86/html/file_module_x86_id_278.html) numbers: ```shell *** Validating build/test_trinary *** === trits_from_trytes: 42320 === === trytes_from_trits: 5103 === *** Validating build/test_curl *** === trits_from_trytes: 220208 ===...

To illustrate the memory impact, [TCMalloc](http://goog-perftools.sourceforge.net/doc/tcmalloc.html) is used for comparisons. The following environment is Intel Xeon E5 class server with Ubuntu Linux `17.04`. First, prepare TCMalloc: `$ sudo apt install...

Dynamic memory allocation tends to be non-deterministic, and is it possible to elininate existing dynamic allocation inside dcurl?

`rdtsc` is not accurate for SMP.

Ouch! It is a pity. I look forward to the migration to other memory allocators.

After #95 is resolved, we can continue memory pool engagement.