From: Jason Wang <jasowang@redhat.com>
To: Qinchuanyu <qinchuanyu@huawei.com>
Cc: "rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"mst@redhat.com" <mst@redhat.com>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"(kvm@vger.kernel.org)" <kvm@vger.kernel.org>,
"(netdev@vger.kernel.org)" <netdev@vger.kernel.org>
Subject: Re: [PATCH] vhost: get 2% performance improved by reducing spin_lock race in vhost_work_queue
Date: Mon, 20 May 2013 11:38:10 +0800 [thread overview]
Message-ID: <51999AA2.8070806@redhat.com> (raw)
In-Reply-To: <5872DA217C2FF7488B20897D84F904E7338FD1E5@nkgeml511-mbx.china.huawei.com>
On 05/20/2013 11:06 AM, Qinchuanyu wrote:
> Right now the wake_up_process func is included in spin_lock/unlock, but it could be done outside the spin_lock.
> I have test it with kernel 3.0.27 and guest suse11-sp2, it provide 2%-3% net performance improved.
>
> Signed-off-by: Chuanyu Qin <qinchuanyu@huawei.com>
Make sense to me but need generate a patch against net-next.git or
vhost.git in git.kernel.org.
Btw. How did you test this? Care to share the perf numbers?
Thanks
> mu
> --- a/drivers/vhost/vhost.c 2013-05-20 10:36:30.000000000 +0800
> +++ b/drivers/vhost/vhost.c 2013-05-20 10:36:54.000000000 +0800
> @@ -144,9 +144,10 @@
> if (list_empty(&work->node)) {
> list_add_tail(&work->node, &dev->work_list);
> work->queue_seq++;
> + spin_unlock_irqrestore(&dev->work_lock, flags);
> wake_up_process(dev->worker);
> - }
> - spin_unlock_irqrestore(&dev->work_lock, flags);
> + } else
> + spin_unlock_irqrestore(&dev->work_lock, flags);
> }
>
> void vhost_poll_queue(struct vhost_poll *poll)
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-20 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 3:06 [PATCH] vhost: get 2% performance improved by reducing spin_lock race in vhost_work_queue Qinchuanyu
2013-05-20 3:38 ` Jason Wang [this message]
2013-05-20 4:15 ` Lei Li
2013-05-20 4:22 ` Qinchuanyu
2013-05-20 4:46 ` Jason Wang
2013-05-21 2:40 ` Qinchuanyu
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=51999AA2.8070806@redhat.com \
--to=jasowang@redhat.com \
--cc=dhowells@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qinchuanyu@huawei.com \
--cc=rusty@rustcorp.com.au \
/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).