All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: ak@suse.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, markus.t.metzger@gmail.com, "Siddha,
	Suresh B" <suresh.b.siddha@intel.com>,
	roland@redhat.com, akpm@linux-foundation.org,
	mtk.manpages@gmail.com, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: x86, ptrace: support for branch trace store(BTS)
Date: Thu, 13 Dec 2007 11:29:39 +0100	[thread overview]
Message-ID: <20071213102939.GS8977@elte.hu> (raw)
In-Reply-To: <029E5BE7F699594398CA44E3DDF554440115D6DC@swsmsx413.ger.corp.intel.com>


* Metzger, Markus T <markus.t.metzger@intel.com> wrote:

> Users who want to process that huge amount of data would be better off 
> using a file-based approach (well, if it cannot be held in physical 
> memory, they will spend most of their time swapping, anyway). Those 
> users would typically wait for the 'buffer full' event and drain the 
> buffer into a file - whether this is the real buffer or a bigger 
> virtual buffer.
> 
> The two-buffer approach would only benefit users who want to hold the 
> full profile in memory - or who want to stall the debuggee until they 
> processed or somehow compressed the data collected so far. Those 
> approaches would not scale for very big profiles. The small profile 
> cases would already be covered with a reasonably big real buffer.

well, the two-buffer approach would just be a general API with no 
limitations. It would make the internal buffer mostly a pure performance 
detail.

	Ingo

  reply	other threads:[~2007-12-13 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 11:38 [patch 1/4] x86: remove bad comment Markus Metzger
2007-12-10 20:20 ` x86, ptrace: support for branch trace store(BTS) Ingo Molnar
2007-12-11 10:34   ` Metzger, Markus T
2007-12-11 14:53     ` Ingo Molnar
2007-12-12  9:18       ` Metzger, Markus T
2007-12-12 11:03         ` Ingo Molnar
2007-12-12 12:23           ` Metzger, Markus T
2007-12-13 10:29             ` Ingo Molnar [this message]
2007-12-13 12:51               ` Metzger, Markus T
2007-12-13 13:08                 ` Ingo Molnar
2007-12-13 16:06                   ` Metzger, Markus T

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=20071213102939.GS8977@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.t.metzger@gmail.com \
    --cc=markus.t.metzger@intel.com \
    --cc=mtk.manpages@gmail.com \
    --cc=roland@redhat.com \
    --cc=stern@rowland.harvard.edu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.