mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Michael Rapoport <RAPOPORT@il.ibm.com>
Cc: Bandan Das <bsd@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	mst@redhat.com, jiangshanlai@gmail.com
Subject: Re: [RFC PATCH 0/4] cgroup aware workqueues
Date: Fri, 27 May 2016 10:17:15 -0400	[thread overview]
Message-ID: <20160527141715.GI23194@mtj.duckdns.org> (raw)
In-Reply-To: <201605270822.u4R8MRoB027943@d06av10.portsmouth.uk.ibm.com>

On Fri, May 27, 2016 at 12:22:19PM +0300, Michael Rapoport wrote:
> I've run two guests without any CPU pinning and without any actual 
> interaction with cgroups
> Here's the results (in MBits/sec):
> 
> size |   64  |   256   |  1024   |  4096   |  16384
> -----+-------+---------+---------+---------+---------
> (1)  | 496.8 | 1346.31 | 6058.49 | 13736.2 | 13541.4
> (2)  | 493.3 | 1604.03 | 5723.68 | 10181.4 | 15572.4
> (3)  | 489.7 | 1437.86 | 6251.12 | 12774.2 | 12867.9 
> 
> 
> From what I see, for different packet sizes there's different approach 
> that outperforms the others.
> Moreover, I'd expect that in case when vhost completely takes over the 
> worker thread there would no be difference vs. current state.
> 
> Tejun, can you help explaining these results? 

Heh, the only thing I can tell is the tests seem noisy and weren't run
enough times to draw any conclusion.  Even if the numbers were
consistent, I don't think anybody would be able to tell a lot from
just the results.  If the results can be made stable, perf would be a
good place to start.

Thanks.

-- 
tejun

      reply	other threads:[~2016-05-27 14:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 22:14 Bandan Das
2016-03-18 22:14 ` [RFC PATCH 1/4] cgroup: Introduce a function to compare two tasks Bandan Das
2016-03-18 22:14 ` [RFC PATCH 2/4] workqueue: introduce support for attaching to cgroups Bandan Das
2016-03-18 22:14 ` [RFC PATCH 3/4] cgroup: use spin_lock_irq for cgroup match and attach fns Bandan Das
2016-03-18 22:14 ` [RFC PATCH 4/4] vhost: use workqueues for the works Bandan Das
2016-03-20 18:10 ` [RFC PATCH 0/4] cgroup aware workqueues Tejun Heo
2016-03-21 17:35   ` Bandan Das
2016-03-21  7:58 ` Michael Rapoport
2016-03-21  8:29 ` Christian Borntraeger
2016-03-21 17:49   ` Bandan Das
     [not found] ` <201603210758.u2L7wiXA028101@d06av09.portsmouth.uk.ibm.com>
2016-03-21 17:43   ` Bandan Das
2016-03-22  7:12     ` vhost threading model (was: Re: [RFC PATCH 0/4] cgroup aware workqueues) Michael Rapoport
     [not found]     ` <201603220712.u2M7CCfq004548@d06av03.portsmouth.uk.ibm.com>
2016-03-22 19:00       ` vhost threading model Bandan Das
2016-03-23 11:13         ` Michael Rapoport
     [not found] ` <201603210758.u2L7wiY9003907@d06av07.portsmouth.uk.ibm.com>
2016-03-30 17:04   ` [RFC PATCH 0/4] cgroup aware workqueues Tejun Heo
2016-03-31  6:17     ` Michael Rapoport
2016-03-31 17:14       ` Tejun Heo
2016-03-31 18:45         ` Bandan Das
2016-04-03 10:43           ` Michael Rapoport
     [not found]           ` <201604031043.u33AhpSF023771@d06av06.portsmouth.uk.ibm.com>
2016-04-04 17:00             ` Bandan Das
2016-04-03 10:43         ` Michael Rapoport
2016-05-27  9:22         ` Michael Rapoport
2016-05-27 14:17           ` Tejun Heo [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=20160527141715.GI23194@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=RAPOPORT@il.ibm.com \
    --cc=bsd@redhat.com \
    --cc=jiangshanlai@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@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

all inboxes | Powered by JetHome®