All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meng Xu <mengxu@cis.upenn.edu>
To: Tianyang Chen <tiche@seas.upenn.edu>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>
Subject: Re: [PATCH 2/2] xen: sched: rtds: use non-atomic bit-ops
Date: Tue, 17 May 2016 11:08:32 -0400	[thread overview]
Message-ID: <CAENZ-+kKb5bB4ueUc2qtt+DPsE2cbCFH9fR6ZVSp6QW72p-jsA@mail.gmail.com> (raw)
In-Reply-To: <1463356490-9780-3-git-send-email-tiche@seas.upenn.edu>

On Sun, May 15, 2016 at 7:54 PM, Tianyang Chen <tiche@seas.upenn.edu> 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@seas.upenn.edu>

Reviewed-by: Meng Xu <mengxu@cis.upenn.edu>

Thanks,

Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-05-17 15:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-15 23:54 [PATCH 0/2] xen: sched: rtds refactor code Tianyang Chen
2016-05-15 23:54 ` [PATCH 1/2] " Tianyang Chen
2016-05-17 15:06   ` Meng Xu
2016-06-22 15:51   ` George Dunlap
2016-06-22 16:16     ` Meng Xu
2016-06-23 10:42       ` George Dunlap
2016-06-24  7:45         ` Dario Faggioli
2016-06-24 11:36           ` Meng Xu
2016-05-15 23:54 ` [PATCH 2/2] xen: sched: rtds: use non-atomic bit-ops Tianyang Chen
2016-05-17 15:08   ` Meng Xu [this message]
2016-05-17 15:05 ` [PATCH 0/2] xen: sched: rtds refactor code Meng Xu

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=CAENZ-+kKb5bB4ueUc2qtt+DPsE2cbCFH9fR6ZVSp6QW72p-jsA@mail.gmail.com \
    --to=mengxu@cis.upenn.edu \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=tiche@seas.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 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.