I've got 4 LITTLE cores and 4 big cores.  In other code I've written for these 
platforms, I've been able to use all 8 cores, to observe interesting behaviour.

I've looked at [this 
thread](https://discuss.tvm.apache.org/t/android-big-little-core-control/2100/3),
 and opinion seems to be mixed, though @eqy seems to think it's possible.  [A 
linked 
thread](https://discuss.tvm.apache.org/t/number-of-threads-used-during-auto-tunning/570/2?u=merrymercy)
 suggests that having code such as:

```
        if self.big_little:
            config_func = self.session.get_function('runtime.config_threadpool')
            # config_func(1, 1) # use 1 big core
            # config_func(1, 2) # use 2 big cores
            #config_func(-1, 1) # use 1 small core
            # config_func(-1, 2) # use 2 small cores
            config_func(4, 4)
```

Might work, however it has not for me.

[This 
thread](https://discuss.tvm.apache.org/t/setting-per-core-usage-explicitly-in-tvm/4538/3)
 discusses binding of threads, but playing around with the environment 
variables has not changed my behaviour.

As the APIs have developed since prior threads, is there now a more canonical 
way of doing this?  I'm not worried about clever load balancing for now, I 
would just like to run with 8 threads.





---
[Visit 
Topic](https://discuss.tvm.apache.org/t/use-all-cores-in-a-big-little-architecture/8474/1)
 to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.apache.org/email/unsubscribe/6b3add9eda6325c93bd1c4115f8575e259571d2efc6d03ef9d79ac16fe55f7b5).

Reply via email to