From: "Jesse Yang" <yzx@baibantech.com.cn>
To: "David Hildenbrand" <david@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, 李珅 <lishen@baibantech.com.cn>,
李计勇 <ljy@baibantech.com.cn>, 王斌 <wb@baibantech.com.cn>
Subject: Re: [RFC] A multithread lockless deduplication engine
Date: Thu, 21 Sep 2017 10:18:14 +0800 [thread overview]
Message-ID: <d783f386-6d48-42bc-be08-473512414dfc.yzx@baibantech.com.cn> (raw)
In-Reply-To: f417f14b-e6b4-ec7a-3ce8-06d039e7dc49@redhat.com
------------------------------------------------------------------
From:David Hildenbrand <david@redhat.com>
Send Time:20/9/2017 23:35
> Can you outline why we can't simply improve KSM? Or is your plan to
> actually improve KSM and it is just the codename "PageONE" ? (haven't
> looked at the code - why 4.4.1 and not upstream linux?)
> --
> Thanks,
>
> David
Thanks for replying!
PageONE is based on a new tree algorithm other than KSM’s red-black tree. The original idea is that we can use a lockless tree to enhance multithread performance. Not all tree algorithms are suitable for this purpose. We have not find a way to do it for red-black tree. PageONE is based on a new tree. The closest topology we found is Patricia tree, but also different. We name it SD tree currently.
The original engine name is ONE (Object Non-duplicate Engine), it is designed for general purpose object deduplication. We applied it to kernel page field (PageONE) first because here we can find out how it behaves in high speed environment.
The details of SD tree are going to be explained in future topics.
Right now, we just choose 4.4.1 to verify PageONE function .
--
Jesse Yang
next prev parent reply other threads:[~2017-09-21 2:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 3:03 [RFC] A multithread lockless deduplication engine XaviLi
2017-09-20 9:36 ` 王金浦
2017-09-20 10:29 ` Jesse Yang
2017-09-20 15:35 ` David Hildenbrand
2017-09-21 2:18 ` Jesse Yang [this message]
2017-09-20 3:23 XaviLi
2017-09-26 11:47 ` Michal Hocko
2017-09-26 11:47 ` Michal Hocko
2017-09-28 10:09 ` Andrea Arcangeli
2017-09-28 10:09 ` Andrea Arcangeli
2017-09-29 9:50 ` XaviLi
2017-09-21 6:45 Jesse Yang
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=d783f386-6d48-42bc-be08-473512414dfc.yzx@baibantech.com.cn \
--to=yzx@baibantech.com.cn \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lishen@baibantech.com.cn \
--cc=ljy@baibantech.com.cn \
--cc=wb@baibantech.com.cn \
/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.