Re: Limitations with v2 port implementation

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1506983097-1428502225=:13976
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On Wed, 8 Apr 2015, Sylvain Joyeux wrote:

>> Agreed, but it doesn=E2=80=99t solve the performance issue.
>
> Definitely not :(.
>
> Just for benchmarking sake, have you done some profiling ? Or have you
> tried using a lock policy instead of lock-free. Lock-free is nice, but
> it looks nasty from an instruction cache p.o.v.

Why "instruction" cache, and not just "cache" in general...?

> Sylvain

Herman
--8323329-1506983097-1428502225=:13976
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev

--8323329-1506983097-1428502225=:13976--