From: Yang Hongyang <hongyang.yang@easystack.cn>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xensource.com
Subject: Re: [Xen 4.7] tmem todos
Date: Wed, 28 Oct 2015 16:18:56 +0800 [thread overview]
Message-ID: <563084F0.5000203@easystack.cn> (raw)
In-Reply-To: <20151027162653.GE27810@l.oracle.com>
On 2015年10月28日 00:26, Konrad Rzeszutek Wilk wrote:
> Hey,
>
> Way back in Shenghai we had a chat about what needs to be done
> in tmem for the 4.6 release. Things got done, but there are other
> things that need to be done:
>
> a) Migration v2 support
> b) Fix the toolstack (cleanup)
> c) tmem tze, dedup, and zlib code drop
> d) simplify the internal structs
> e) Make it work on 5TB and higher
> f) And finally security audit.
>
> In 4.6 I did an conversion of moving the sysctl related tmem
> to the sysctl hypercall. That cleaned up the code a bit and made
> it fit nicer in the appropiate architecture bins.
>
> The next step will be to follow that and actually seperate
> the tmem C code - one file for sysctl and the other for tmem operations.
>
> That will allow me to focus then on the b), and c) part.
> a) is going to be the stretch goal that I will try to get done
> (at least an RFC). The nice side benefit is that I will be better
> equipped to review the REMUS patches so an extra reviewer.
That's great! :)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
--
Thanks,
Yang
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-10-28 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 16:26 [Xen 4.7] tmem todos Konrad Rzeszutek Wilk
2015-10-28 8:18 ` Yang Hongyang [this message]
2015-10-28 13:29 ` Konrad Rzeszutek Wilk
2015-10-30 1:05 ` Yang Hongyang
2015-10-30 15:06 ` 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=563084F0.5000203@easystack.cn \
--to=hongyang.yang@easystack.cn \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.