All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:45:49 +0800	[thread overview]
Message-ID: <99b920e3-3c2c-41bb-94a3-e174e87b9b35.yzx@baibantech.com.cn> (raw)

------------------------------------------------------------------
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


During the development process, we switch over serval kernel versions, switching version is relatively simple.

So we haven't see updating kernel version as a pushing issue. if anyone  needs the  patch for other kernel versions, please name it.

--
Jesse Yang

             reply	other threads:[~2017-09-21  6:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  6:45 Jesse Yang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-20  3:23 [RFC] A multithread lockless deduplication engine 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-20  3:03 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

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=99b920e3-3c2c-41bb-94a3-e174e87b9b35.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.