From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: netdev <netdev@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Tejun Heo <tj@kernel.org>, Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: Make vhost multi-threaded and associate each thread to its guest's cgroup
Date: Wed, 28 Jul 2010 04:12:04 +0300 [thread overview]
Message-ID: <20100728011203.GA22999@redhat.com> (raw)
In-Reply-To: <1280277701.27059.11.camel@w-sridhar.beaverton.ibm.com>
On Tue, Jul 27, 2010 at 05:41:41PM -0700, Sridhar Samudrala wrote:
> On Tue, 2010-07-27 at 23:42 +0300, Michael S. Tsirkin wrote:
> > Sridhar,
> > I pushed a patchset with all known issues fixed,
> > on my vhost-net-next branch.
> >
> > For now this ignores the cpu mask issue, addressing
> > only the cgroups issue.
> >
> > Would appreciate testing and reports.
>
> I had to apply the following patch to get it build.
> With this patch, i am seeing similar results as i saw earlier.
>
> Thanks
> Sridhar
Excellent, thanks for the testing.
> diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
> index 996e751..8543898 100644
> --- a/drivers/vhost/vhost.c
> +++ b/drivers/vhost/vhost.c
> @@ -23,6 +23,7 @@
> #include <linux/highmem.h>
> #include <linux/slab.h>
> #include <linux/kthread.h>
> +#include <linux/cgroup.h>
>
> #include <linux/net.h>
> #include <linux/if_packet.h>
> @@ -252,7 +253,7 @@ static long vhost_dev_set_owner(struct vhost_dev *dev)
> }
>
> dev->worker = worker;
> - err = cgroup_attach_task_current_cg(poller);
> + err = cgroup_attach_task_current_cg(worker);
> if (err)
> goto err_cgroup;
> wake_up_process(worker); /* avoid contributing to loadavg */
>
prev parent reply other threads:[~2010-07-28 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 20:42 Make vhost multi-threaded and associate each thread to its guest's cgroup Michael S. Tsirkin
2010-07-28 0:41 ` Sridhar Samudrala
2010-07-28 1:12 ` Michael S. Tsirkin [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=20100728011203.GA22999@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).