[Xen 4.7] tmem todos

[Xen 4.7] tmem todos

[Konrad Rzeszutek Wilk]

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.

Re: [Xen 4.7] tmem todos

[Yang Hongyang]

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

Re: [Xen 4.7] tmem todos

[Konrad Rzeszutek Wilk]

On Wed, Oct 28, 2015 at 04:18:56PM +0800, Yang Hongyang wrote:
> 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! :)

Yeah! BTW, I haven't seen those patches lately. Any idea when
they would be posted?
> 
> >
> >
> >_______________________________________________
> >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

Re: [Xen 4.7] tmem todos

[Yang Hongyang]

On 2015年10月28日 21:29, Konrad Rzeszutek Wilk wrote:
> On Wed, Oct 28, 2015 at 04:18:56PM +0800, Yang Hongyang wrote:
>> 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! :)
>
> Yeah! BTW, I haven't seen those patches lately. Any idea when
> they would be posted?

Ah, you mean COLO series, let's Cc Congyang...

>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
>>>
>>
>> --
>> Thanks,
>> Yang
>

-- 
Thanks,
Yang

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

Re: [Xen 4.7] tmem todos

[Konrad Rzeszutek Wilk]

On Fri, Oct 30, 2015 at 09:05:29AM +0800, Yang Hongyang wrote:
> On 2015年10月28日 21:29, Konrad Rzeszutek Wilk wrote:
> >On Wed, Oct 28, 2015 at 04:18:56PM +0800, Yang Hongyang wrote:
> >>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! :)
> >
> >Yeah! BTW, I haven't seen those patches lately. Any idea when
> >they would be posted?
> 
> Ah, you mean COLO series, let's Cc Congyang...

Either way - whatever touches migration code.

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