All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Wang2 <wei.wang2@amd.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: robert.richter@amd.com,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2/2] xenoprofile: Add IBS support
Date: Tue, 10 Aug 2010 14:44:48 +0200	[thread overview]
Message-ID: <201008101444.49811.wei.wang2@amd.com> (raw)
In-Reply-To: <4C600577020000780000ED13@vpn.id2.novell.com>

On Monday 09 August 2010 13:41:11 Jan Beulich wrote:
> >>> On 30.07.10 at 15:28, Wei Wang2 <wei.wang2@amd.com> wrote:
> >
> >--- a/drivers/oprofile/oprofile_files.c
> >+++ b/drivers/oprofile/oprofile_files.c
> >@@ -21,7 +21,7 @@
> > #include "oprof.h"
> >
> > unsigned long fs_buffer_size = 131072;
> >-unsigned long fs_cpu_buffer_size = 8192;
> >+unsigned long fs_cpu_buffer_size = 131072;
>
> Why is this needed at all, why this much of an increase, and why not
> conditional upon CONFIG_XEN?
>
> Jan


Hi Jan
I had observed over 50% samples lose using following configuration:
opcontrol --start --event=IBS_OP_ALL:50000 --no-vmlinux
if fs_cpu_buffer_size = 8192. The same issue was also seen on native 2.6.34 
kernel. In my case, extending fs_cpu_buffer_size or increasing sampling 
period can fix this issue.

Since each IBS_OP sample will occupy 14 entries in cpu buffer compared with 
only 1 entry for event-based sample, I suspect that the default size of 
per-cpu buffer would not be enough for IBS_OP mode in minimum sampling period 
(50000). I simply extended fs_cpu_buffer_size just to make sure it works for 
current userland tools. If we intent to force a longer minimum sampling 
period for IBS_OP_ALL in future release of tools, we could keep 
fs_cpu_buffer_size = 8192.

Thanks,
Wei

      reply	other threads:[~2010-08-10 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30 13:28 [PATCH 2/2] xenoprofile: Add IBS support Wei Wang2
2010-08-09 11:41 ` Jan Beulich
2010-08-10 12:44   ` Wei Wang2 [this message]

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=201008101444.49811.wei.wang2@amd.com \
    --to=wei.wang2@amd.com \
    --cc=JBeulich@novell.com \
    --cc=robert.richter@amd.com \
    --cc=xen-devel@lists.xensource.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 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.