From: Wei Liu <wei.liu2@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH v1 for 4.7] Tmem cleanups.
Date: Thu, 2 Jun 2016 16:42:12 +0100 [thread overview]
Message-ID: <20160602154212.GD5714@citrix.com> (raw)
In-Reply-To: <1464879860-25554-1-git-send-email-konrad.wilk@oracle.com>
On Thu, Jun 02, 2016 at 11:04:16AM -0400, Konrad Rzeszutek Wilk wrote:
> Hey!
>
> Since RFC [http://www.gossamer-threads.com/lists/xen/devel/431812]
> - Added Reviewed-by from Doug
> - Dropped the RFC
>
>
> 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
> step in this cleanup. (See
> http://lists.xen.org/archives/html/xen-devel/2015-10/msg03313.html)
> which will allow me to follow up on the other steps:
> b) Fix the toolstack (cleanup)
> c) tmem tze, dedup, and zlib code drop
>
> Anyhow sorry for this being so tardy - xSplice had more attention :-)
>
What do you mean here? There is no such thing called xSplice! :-P
> Regression tests show no problems.
>
> The patches themselves have no functionality changes thought I was itching
> to remove most of the counters. I will do that going forward, but need
> to figure out which ones make sense or if some of them can be coalesced.
>
>
> xen/common/Makefile | 2 +-
> xen/common/tmem.c | 618 +++++------------------------------------
> xen/common/tmem_control.c | 443 +++++++++++++++++++++++++++++
> xen/include/xen/tmem_control.h | 33 +++
> xen/include/xen/tmem_xen.h | 128 +++++++++
> 5 files changed, 672 insertions(+), 552 deletions(-)
>
Since this is only tmem code, the only risk is it doesn't build in
osstest, but I think the probability is quite low.
If you confirm that it builds on Debian Jessie, that would be good
enough for me:
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
> Konrad Rzeszutek Wilk (4):
> tmem: Move global stats in a tmem_statistics structure
> tmem: Wrap atomic_t in struct tmem_statistics as well.
> tmem: Move global_ individual variables in a global structure.
> tmem: Move bulk of tmem control functions in its own file.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-02 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 15:04 [PATCH v1 for 4.7] Tmem cleanups Konrad Rzeszutek Wilk
2016-06-02 15:04 ` [PATCH v1 1/4] tmem: Move global stats in a tmem_statistics structure Konrad Rzeszutek Wilk
2016-06-02 15:04 ` [PATCH v1 2/4] tmem: Wrap atomic_t in struct tmem_statistics as well Konrad Rzeszutek Wilk
2016-06-02 15:16 ` Andrew Cooper
2016-06-02 15:26 ` Konrad Rzeszutek Wilk
2016-06-02 15:04 ` [PATCH v1 3/4] tmem: Move global_ individual variables in a global structure Konrad Rzeszutek Wilk
2016-06-02 15:04 ` [PATCH v1 4/4] tmem: Move bulk of tmem control functions in its own file Konrad Rzeszutek Wilk
2016-06-02 15:17 ` [PATCH v1 for 4.7] Tmem cleanups Jan Beulich
2016-06-02 15:27 ` Konrad Rzeszutek Wilk
2016-06-02 15:42 ` Wei Liu [this message]
2016-06-02 15:46 ` Konrad Rzeszutek Wilk
2016-06-02 20:09 ` 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=20160602154212.GD5714@citrix.com \
--to=wei.liu2@citrix.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).