The perf tool, like the Linux one, allows you to select the CPUs where you want your program, and your counters, to tick. This is why I am asking. The default CPU set is the low latency set (currently only #0), but the user can select to run its program, and counters, on a different CPU set. And I use sys_provision for that.
On Wed, Dec 2, 2015 at 8:59 AM, Barret Rhoden <[email protected]> wrote: > On 2015-12-02 at 08:50 "'Davide Libenzi' via Akaros" > <[email protected]> wrote: > > Is there some already done test program which runs for a little bit, > > and spreads across the provisioned cores (using threads)? > > I need to test the new perf, and I'd rather use and existing test > > program, instead of writing one. > > Oh, and possibly that does not use the network, because it's busted > > on the Akaros boxes. > > The most basic program we have like that is pthread_test. The > primary arguments are nr_threads, nr_loops, nr_vcores. > > It won't do anything with provisioning though; something external will > need to do that. I'm not sure what exactly you're doing, but you might > not need to deal with provisioning. I guess we'll see. > > I've mucked around with scripts that will provision and preempt cores > between a couple processes (mostly used in testing the PDR locks). > kern/kfs/lockprov.sh might have some pointers. > > -- > You received this message because you are subscribed to the Google Groups > "Akaros" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
