public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@linuxtv.org>
To: Marko Ristola <marko.ristola@kolumbus.fi>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Speed up DVB TS stream delivery from DMA buffer into dvb-core's buffer
Date: Sun, 10 Apr 2011 14:28:31 +0200	[thread overview]
Message-ID: <4DA1A26F.2010305@linuxtv.org> (raw)
In-Reply-To: <4D9F63E1.6060808@kolumbus.fi>

On 04/08/2011 09:37 PM, Marko Ristola wrote:
> 
> Here is some statistics without likely and with likely functions.
> 
> It seems that using likely() gives better performance with Phenom I too.

I'm not sure whether that's the right conclusion. See below.

> 	%	Plain knl %	No likely	%	With likely	%
> dvb_ringbuffer_write		5,9	62,8	8,7	81,3	5,7	79,2
> dvb_dmx_swfilter_packet	1,2	12,8	0,7	6,5	0,8	11,1
> dvb_dmx_swfilter_204		2,3	24,5	1,3	12,1	0,7	9,7
> 
> 
> Here "Plain knl %" is "perf top -d 30" percentage.
> 24,5 12,1 and 9,7 are percentages without a patch, with basic patch
> and last is with "likely" functions using patch.

The varying ratio between dvb_ringbuffer_write and
dvb_dmx_swfilter_packet, which haven't been modified by the patch, seems
to indicate that the numbers were influenced by other activities on the
system or by the data used during the tests. 8,7% for
dvb_ringbuffer_write in test #2 could also indicate a higher data rate
than in #1 and #3.

However, adding likely() certainly won't do any harm. Feel free to send
an incremental patch.

Regards,
Andreas

  reply	other threads:[~2011-04-10 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 15:40 [PATCH] Speed up DVB TS stream delivery from DMA buffer into dvb-core's buffer Marko Ristola
2011-04-08 19:37 ` Marko Ristola
2011-04-10 12:28   ` Andreas Oberritter [this message]
2011-04-10 12:10 ` Andreas Oberritter

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=4DA1A26F.2010305@linuxtv.org \
    --to=obi@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    --cc=marko.ristola@kolumbus.fi \
    --cc=mchehab@redhat.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