[CentOS-devel] Multipath-TCP in the centosplus kernel?

Steve Clark

sclark at netwolves.com
Wed Jun 18 10:46:13 UTC 2014


On 06/17/2014 04:01 PM, Johnny Hughes wrote:
> On 06/17/2014 03:00 PM, Johnny Hughes wrote:
>> On 06/17/2014 02:51 PM, Guillaume Derval wrote:
>>> Le 17 juin 2014 à 19:57, Akemi Yagi <amyagi at gmail.com> a écrit :
>>>> With my initial concern gone, I now have more practical question.
>>>>
>>>> The modifications are quite extensive as noted in the beginning. I
>>>> count 15 patches in include/ and 29 in /net . For each kernel update,
>>>> the patch set must be updated/tested. Also there may be updates to the
>>>> patches themselves within a given kernel release. How can this be best
>>>> handled? Could dealing with the patches cause a delay in the cplus
>>>> kernel release?
>>>>
>>>> Having a separate kernel addressing the mptcp stuff might work around
>>>> that potential issue.
>>>>
>>>> Akemi
>>> I personally think that creating a separate kernel (kernel-cplus-mptcp? :-) ) is the best thing to do.
>>>
>> I think a separate kernel might be best too.
>>
>> It can be kernel-mptcp and live in centos-plus if we choose to do
>> kernel-plus, kernel-<some_name>, etc. or we can do it another way, but
>> regardless in a separate kernel is likely best.
> That also means that someone (or someones) need to volunteer to maintain
> it as well.

Would it be a distro kernel with only the mptcp added or would it be a "plus" kernel with mptcp?

Thanks,

-- 
Stephen Clark
*NetWolves Managed Services, LLC.*
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.clark at netwolves.com
http://www.netwolves.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140618/c85eb594/attachment-0003.html>


More information about the CentOS-devel mailing list