From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3020DC433E7 for ; Sun, 18 Oct 2020 16:35:41 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 9999120874 for ; Sun, 18 Oct 2020 16:35:40 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Q4qDZLOV" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9999120874 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 1ABCA6B006C; Sun, 18 Oct 2020 12:35:40 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 15BDD6B006E; Sun, 18 Oct 2020 12:35:40 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 024026B0070; Sun, 18 Oct 2020 12:35:39 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0095.hostedemail.com [216.40.44.95]) by kanga.kvack.org (Postfix) with ESMTP id CB3D86B006C for ; Sun, 18 Oct 2020 12:35:39 -0400 (EDT) Received: from smtpin20.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 7A9693629 for ; Sun, 18 Oct 2020 16:35:39 +0000 (UTC) X-FDA: 77385597198.20.smoke80_4d14ffc2722f Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin20.hostedemail.com (Postfix) with ESMTP id 5B6D7180C07A3 for ; Sun, 18 Oct 2020 16:35:39 +0000 (UTC) X-HE-Tag: smoke80_4d14ffc2722f X-Filterd-Recvd-Size: 9160 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by imf14.hostedemail.com (Postfix) with ESMTP for ; Sun, 18 Oct 2020 16:35:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1603038938; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=SwtWnuB2kSY8HFQICilrmvB9NiLAnGrV11+EFgQMsrc=; b=Q4qDZLOVdUKrUF0fRdThG4qZSJLz3Hmpr/tOKhjrXCgczOfO7VqEHDmKcDW6yoi2lCMSYK PnE5eZ3yVAwxUMXbFArUUruXw1lIvHWoETfOe/U6NESMfmH8YlpXWTdNQ0Jj+ZtbPOvTTC oqdA/fuHp1rUhdVga+fQ8Yf4A/XT1ZM= Received: from mail-ej1-f69.google.com (mail-ej1-f69.google.com [209.85.218.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-316-ny9UJj2lP76H-RuCTMGSnw-1; Sun, 18 Oct 2020 12:35:32 -0400 X-MC-Unique: ny9UJj2lP76H-RuCTMGSnw-1 Received: by mail-ej1-f69.google.com with SMTP id j7so3676629ejy.7 for ; Sun, 18 Oct 2020 09:35:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=RY0f+Ml007JAsH07kY6MGpcOC0lcirSpPFKLKx43wmI=; b=JmOeCZP6WLIylcoSvneRQ5619UCE1wyYLu2+mBXa5O/+yHxdvltugzZ//SfWZEdx5u 1885a/0oDxo8GMulN+Aj9d9vzH4e3xiVgedSO13P/ouhNinnqfSZ6UYz1w/OJmbDvPi5 QbgqCTw2KWivWIENP90T1HTS8p0/FB3FjHQVFnP4xaEA2zFaRSvEY4QVCv5P7Ycx//+4 98NNDOO9HawFF3dD4VsIZ6kgawis5Y7QK8Fw+RmR1MakrvYvmjaZWtI+nL5KpzQ6X9d/ UZJrdPWRwNRXFTn3apNLTjV5Q3s1GeqGtjXEdUNO+kJGLnlAHPfQ/NC2H9jYc8WCrSZD eExQ== X-Gm-Message-State: AOAM531Z1BRjJClV/MXlRK8Ie2nZ8vw71YyfkmAcv9siav45GqOkJyPs NqRff/v9UhvtLUZamodS7z9VYDndbZdfosiTovlU0RUd8Pvdt8qtKwYHxzStkyGYQUC0yR05+Fo jMeDhCpcrFt4= X-Received: by 2002:a17:906:f2d2:: with SMTP id gz18mr13312086ejb.542.1603038931383; Sun, 18 Oct 2020 09:35:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxi1qZzl/6znUyZOzcb/F4zOcFn3HuKD3/8mDE/7uN9jKVozUvtrDX4cd3jS1AGLUL8Kc3Vpg== X-Received: by 2002:a17:906:f2d2:: with SMTP id gz18mr13312066ejb.542.1603038931204; Sun, 18 Oct 2020 09:35:31 -0700 (PDT) Received: from [192.168.3.114] (p4ff233d0.dip0.t-ipconnect.de. [79.242.51.208]) by smtp.gmail.com with ESMTPSA id 59sm7524881ede.73.2020.10.18.09.35.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 18 Oct 2020 09:35:30 -0700 (PDT) From: David Hildenbrand Mime-Version: 1.0 (1.0) Subject: Re: [PATCH v1 00/29] virtio-mem: Big Block Mode (BBM) Date: Sun, 18 Oct 2020 18:35:30 +0200 Message-Id: <045CE408-5E44-4334-8FC2-2C6E88D4EA07@redhat.com> References: <20201018124954.GA51680@L-31X9LVDL-1304.local> Cc: David Hildenbrand , linux-kernel@vger.kernel.org, linux-mm@kvack.org, virtualization@lists.linux-foundation.org, Andrew Morton , "Michael S . Tsirkin" , Jason Wang , Michal Hocko , Oscar Salvador , Pankaj Gupta In-Reply-To: <20201018124954.GA51680@L-31X9LVDL-1304.local> To: Wei Yang X-Mailer: iPhone Mail (18A393) Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=david@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary=Apple-Mail-763CD893-7BF7-4854-9F45-FB7ED5189371 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: --Apple-Mail-763CD893-7BF7-4854-9F45-FB7ED5189371 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > Am 18.10.2020 um 14:50 schrieb Wei Yang : >=20 > =EF=BB=BFOn Mon, Oct 12, 2020 at 02:52:54PM +0200, David Hildenbrand wrot= e: >> virtio-mem currently only supports device block sizes that span at most >> a single Linux memory block. For example, gigantic pages in the hypervis= or >> result on x86-64 in a device block size of 1 GiB - when the Linux memory >> block size is 128 MiB, we cannot support such devices (we fail loading t= he >> driver). Of course, we want to support any device block size in any Linu= x >> VM. >>=20 >> Bigger device block sizes will become especially important once supporti= ng >> VFIO in QEMU - each device block has to be mapped separately, and the >> maximum number of mappings for VFIO is 64k. So we usually want blocks in >> the gigabyte range when wanting to grow the VM big. >>=20 >> This series: >> - Performs some cleanups >> - Factors out existing Sub Block Mode (SBM) >> - Implements memory hot(un)plug in Big Block Mode (BBM) >>=20 >> I need one core-mm change, to make offline_and_remove_memory() eat bigge= r >> chunks. >>=20 >> This series is based on "next-20201009" and can be found at: >> git@gitlab.com:virtio-mem/linux.git virtio-mem-dbm-v1 >>=20 >=20 > I am trying to apply this patch set, while found I can't 'git fetch' this > repo. Is there any other repo I would apply this patch set? >=20 Sorry I tool the wrong repo. It=E2=80=98s on my github: https://github.com/davidhildenbrand/linux/tree/virtio-mem-dbm-v1 > --=20 > Wei Yang > Help you, Help me >=20 --Apple-Mail-763CD893-7BF7-4854-9F45-FB7ED5189371 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Am 18.10.2020 um 14:50 schrieb Wei Yang <richard.weiyang@linux= .alibaba.com>:

=EF=BB=BFOn Mon, Oct 12, 2020 at 02:52:54PM +0200, David = Hildenbrand wrote:
virtio-mem cur= rently only supports device block sizes that span at most
a single Linux memory block. For exam= ple, gigantic pages in the hypervisor
result on x86-64 in a device block size of 1 GiB - when t= he Linux memory
bloc= k size is 128 MiB, we cannot support such devices (we fail loading the
driver). Of course, we w= ant to support any device block size in any Linux
VM.

Big= ger device block sizes will become especially important once supporting
VFIO in QEMU - each dev= ice block has to be mapped separately, and the
maximum number of mappings for VFIO is 64k. So w= e usually want blocks in
<= span>the gigabyte range when wanting to grow the VM big.

This series:
- Performs some cleanups
- Factors out existing Sub Block Mode (SBM)
- Implements memory hot(un)plug in = Big Block Mode (BBM)

I need one core-mm= change, to make offline_and_remove_memory() eat bigger
chunks.

<= span>This series is based on "next-20201009" and can be found at:
   git@gitlab.com:= virtio-mem/linux.git virtio-mem-dbm-v1


I am tryi= ng to apply this patch set, while found I can't 'git fetch' this
= repo. Is there any other repo I would apply this patch set?

Sorry I tool the w= rong repo. It=E2=80=98s on my github:


--
Wei Yang
Help you, Help me

--Apple-Mail-763CD893-7BF7-4854-9F45-FB7ED5189371--