From: Dario Faggioli <dario.faggioli@citrix.com>
To: Tianyang Chen <tiche@cis.upenn.edu>, xen-devel@lists.xenproject.org
Cc: george.dunlap@citrix.com, mengxu@cis.upenn.edu
Subject: Re: [PATCH v2 2/2] xen: sched: rtds: use non-atomic bit-ops
Date: Wed, 29 Jun 2016 18:44:30 +0200 [thread overview]
Message-ID: <1467218670.18298.29.camel@citrix.com> (raw)
In-Reply-To: <1466902114-21694-3-git-send-email-tiche@cis.upenn.edu>
[-- Attachment #1.1: Type: text/plain, Size: 640 bytes --]
On Sat, 2016-06-25 at 20:48 -0400, Tianyang Chen wrote:
> Vcpu flags are checked and cleared atomically. Performance can be
> improved with corresponding non-atomic versions since schedule.c
> already has spin_locks in place.
>
> Signed-off-by: Tianyang Chen <tiche@cis.upenn.edu>
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-06-29 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 0:48 [PATCH v2 0/2] xen: sched: rtds clean-up Tianyang Chen
2016-06-26 0:48 ` [PATCH v2 1/2] xen: sched: rtds code clean-up Tianyang Chen
2016-06-29 16:21 ` Dario Faggioli
2016-06-26 0:48 ` [PATCH v2 2/2] xen: sched: rtds: use non-atomic bit-ops Tianyang Chen
2016-06-29 16:44 ` Dario Faggioli [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=1467218670.18298.29.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=mengxu@cis.upenn.edu \
--cc=tiche@cis.upenn.edu \
--cc=xen-devel@lists.xenproject.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).