From: Bandan Das <bsd@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: tj@kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
mst@redhat.com, jiangshanlai@gmail.com, RAPOPORT@il.ibm.com
Subject: Re: [RFC PATCH 0/4] cgroup aware workqueues
Date: Mon, 21 Mar 2016 13:49:55 -0400 [thread overview]
Message-ID: <jpga8lr67r0.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <56EFB0E0.2080405@de.ibm.com> (Christian Borntraeger's message of "Mon, 21 Mar 2016 09:29:20 +0100")
Christian Borntraeger <borntraeger@de.ibm.com> writes:
> On 03/18/2016 11:14 PM, Bandan Das wrote:
> [..]
>> Netperf:
>> Two guests running netperf in parallel.
>> Without patches With patches
>>
>> TCP_STREAM (10^6 bits/second) 975.45 978.88
>> TCP_RR (Trans/second) 20121 18820.82
>> UDP_STREAM (10^6 bits/second) 1287.82 1184.5
>> UDP_RR (Trans/second) 20766.72 19667.08
>> Time a 4G iso download 2m 33 seconds 3m 02 seconds
>
> So TCP stream stays the same everything else shows a regression? Not good.
> Have you an idea why this happens?
I am not sure yet but my guess is the way these patches implement cgroup
support. I will run some tests just with workqueues (and without these patches) and
see if the newer numbers are consistent with these.
next prev parent reply other threads:[~2016-03-21 17:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 22:14 [RFC PATCH 0/4] cgroup aware workqueues 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 7:58 ` Michael Rapoport
2016-03-21 7:58 ` Michael Rapoport
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
2016-03-22 19:00 ` vhost threading model Bandan Das
2016-03-23 11:13 ` Michael Rapoport
2016-03-23 11:13 ` Michael Rapoport
2016-03-22 7:12 ` vhost threading model (was: Re: [RFC PATCH 0/4] cgroup aware workqueues) Michael Rapoport
2016-03-22 7:12 ` Michael Rapoport
2016-03-21 8:29 ` [RFC PATCH 0/4] cgroup aware workqueues Christian Borntraeger
2016-03-21 17:49 ` Bandan Das [this message]
[not found] ` <201603210758.u2L7wiY9003907@d06av07.portsmouth.uk.ibm.com>
2016-03-30 17:04 ` Tejun Heo
2016-03-31 6:17 ` Michael Rapoport
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
2016-04-03 10:43 ` Michael Rapoport
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-04-03 10:43 ` Michael Rapoport
2016-05-27 9:22 ` Michael Rapoport
2016-05-27 14:17 ` Tejun Heo
2016-05-27 9:22 ` Michael Rapoport
2016-03-31 6:17 ` Michael Rapoport
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=jpga8lr67r0.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=RAPOPORT@il.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=jiangshanlai@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=tj@kernel.org \
/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.