From: Wei Liu <wei.liu2@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, wei.liu2@citrix.com,
jbeulich@suse.com, andrew.cooper3@citrix.com
Subject: Re: [PATCH RFC] Tmem cleanups for 4.7 (hopefully?).
Date: Tue, 17 May 2016 18:15:27 +0100 [thread overview]
Message-ID: <20160517171527.GV8974@citrix.com> (raw)
In-Reply-To: <1463414311-10677-1-git-send-email-konrad.wilk@oracle.com>
On Mon, May 16, 2016 at 11:58:27AM -0400, Konrad Rzeszutek Wilk wrote:
> Hey,
>
> These four little cleanups move the bulk of tmem control ops
> from tmem.c to tmem_control.c.
>
> Last release I moved the control tmem ops from being part of tmem
> hypercall to be part of the syscall subops - and this is the next
This needs review or ack from other HV maintainers.
Since TMEM is still experimental and pretty well isolated so I don't
mind having some code churns in it at this stage.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-17 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 15:58 [PATCH RFC] Tmem cleanups for 4.7 (hopefully?) Konrad Rzeszutek Wilk
2016-05-16 15:58 ` [PATCH RFC 1/4] tmem: Move global stats in a tmem_statistics structure Konrad Rzeszutek Wilk
2016-05-18 1:57 ` Doug Goldstein
2016-05-18 2:01 ` Doug Goldstein
2016-05-18 14:34 ` Konrad Rzeszutek Wilk
2016-05-18 16:30 ` Doug Goldstein
2016-05-16 15:58 ` [PATCH RFC 2/4] tmem: Wrap atomic_t in struct tmem_statistics as well Konrad Rzeszutek Wilk
2016-05-16 15:58 ` [PATCH RFC 3/4] tmem: Move global_ individual variables in a global structure Konrad Rzeszutek Wilk
2016-05-16 15:58 ` [PATCH RFC 4/4] tmem: Move bulk of tmem control functions in its own file Konrad Rzeszutek Wilk
2016-05-17 17:15 ` Wei Liu [this message]
2016-05-18 2:11 ` [PATCH RFC] Tmem cleanups for 4.7 (hopefully?) Doug Goldstein
2016-05-18 14:36 ` Konrad Rzeszutek Wilk
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=20160517171527.GV8974@citrix.com \
--to=wei.liu2@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--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).