Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: andrew.mcdermott@windriver.com (Andrew McDermott)
Subject: [ltt-dev] limiting LTTng to a certain set of cores
Date: Thu, 12 Feb 2009 11:53:16 +0000	[thread overview]
Message-ID: <v4skmjx45v.fsf@swi-aim.swindon.wrsec.fr> (raw)
In-Reply-To: <20090211175539.GE26549@Krystal> (Mathieu Desnoyers's message of "Wed, 11 Feb 2009 12:55:39 -0500")


> * Andrew McDermott (andrew.mcdermott at windriver.com) wrote:
>> 
>> Is there an easy way to limit LTTng to trace a specified set of cores
>> only?  I ask because in some 64+ core systems the data set collected
>> becomes too large for analysis and the tasks to be analyzed are always
>> bound to certain cores (using affinity).
>> 
>> I'm anticipating that this would require changes to LTTng - what I would
>> like to know is how invasive those changes would need to be.
>> 
>
> Hi Andrew,
>
> Basically, this could be done on a per tracing-session/per-channel basis
> by adding an "active core" bit mask to test within ltt_vtrace and
> ltt_serialize_data, in the loop where it iterates on active traces and
> calls the "filter" callback. This bitmask would sit within the channel
> structure. Setting the active cores should be added to the debugfs
> interface :

Thanks for the info!

Perhaps it is something to consider for a future release.

One of the issues I'm facing is that the trace is large and by large I
mean I have to transfer the trace in its entirety from a remote
location.  If I could collect on a subset of the cores then I would have
less to transfer (over my very slow link).

>
> People would do :
> echo tracename > /mnt/debugfs/ltt/setup_trace
> echo CPUNR > /mnt/debugfs/ltt/control/tracename/channel/channelname/cpus
> cat /mnt/debugfs/ltt/control/tracename/channel/channelname/cpus
> ...
>
> Maybe we should replace the "enable" test by a cpu mask test with all
> cpus active to save some cycles...
>
> And I don't particularly care about the exact debugfs file interface
> (file name, the way the cpus are listed). Ideally if we can find
> somewhere else in the Linux kernel where it is already done, that would
> be a great inspiration source.
>
> Thanks,
>
> Mathieu
>
>> Thanks,
>> Andy.
>> 
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>> 

-- 
andy




  reply	other threads:[~2009-02-12 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  9:32 Andrew McDermott
2009-02-11 17:55 ` Mathieu Desnoyers
2009-02-12 11:53   ` Andrew McDermott [this message]
2009-02-11 17:58 ` Pierre-Marc Fournier
2009-02-12 11:50   ` Andrew McDermott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v4skmjx45v.fsf@swi-aim.swindon.wrsec.fr \
    --to=andrew.mcdermott@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox