All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Mike Galbraith <efault@gmx.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Richard Jones <rick.jones2@hp.com>
Subject: Re: Netperf UDP_STREAM regression due to not sending IPIs in ttwu_queue()
Date: Tue, 02 Oct 2012 15:48:57 -0700	[thread overview]
Message-ID: <506B6F59.8060800@hp.com> (raw)
In-Reply-To: <20121002084501.GL29125@suse.de>

On 10/02/2012 01:45 AM, Mel Gorman wrote:

> SIZE=64
> taskset -c 0 netserver
> taskset -c 1 netperf -t UDP_STREAM -i 50,6 -I 99,1 -l 20 -H 127.0.0.1 -- -P 15895 -s 32768 -S 32768 -m $SIZE -M $SIZE

Just FYI, unless you are running a hacked version of netperf, the "50" 
in "-i 50,6" will be silently truncated to 30.

happy benchmarking,

rick jones

PS - I trust it is the receive-side throughput being reported/used with 
UDP_STREAM :)

  parent reply	other threads:[~2012-10-02 22:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02  6:51 Netperf UDP_STREAM regression due to not sending IPIs in ttwu_queue() Mel Gorman
2012-10-02  7:49 ` Mike Galbraith
2012-10-02  8:45   ` Mel Gorman
2012-10-02  9:31     ` Mike Galbraith
2012-10-02 13:14       ` Mel Gorman
2012-10-02 14:33         ` Mike Galbraith
2012-10-03  6:50         ` Mike Galbraith
2012-10-03  8:13           ` Mike Galbraith
2012-10-03 13:30             ` Mike Galbraith
2012-10-10 12:29               ` Mel Gorman
2012-10-10 13:02                 ` Mike Galbraith
2012-10-10 13:05                 ` Peter Zijlstra
2012-10-02 22:48     ` Rick Jones [this message]
2012-10-03  9:47       ` Mel Gorman
2012-10-03 10:22         ` Eric Dumazet
2012-10-03 18:04         ` Rick Jones
2012-10-05  9:54           ` Mel Gorman

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=506B6F59.8060800@hp.com \
    --to=rick.jones2@hp.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=suresh.b.siddha@intel.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.