Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp2292830pxb; Mon, 19 Apr 2021 02:04:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwT7LiMPkh6qnaeGjEsgHgWOoph2ODochtek2vgmOo5IkylRQl09IyuKeVTGQyqjg0LNtiZ X-Received: by 2002:a05:6402:11c9:: with SMTP id j9mr24167790edw.348.1618823055891; Mon, 19 Apr 2021 02:04:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618823055; cv=none; d=google.com; s=arc-20160816; b=AYs/r+36d4POzYZ71rnvlRI3aXT4RPrxnABX4AmIqpmXq6GYH/UIZiYr72FQiF/u76 DbJj0oiIA8CVorfJSPnMwqJTbKAF/AvKStQRsG8bILXjaLauANUov5IZlY1Rukf9R9PU dKqx9yw4Cb0bIBm58vq2W3pPt777A6q5jbWyTxWS9nqhVbi6bb7pup8XfjbE7X5IfY/A Qb+zNzsTyXbd64Bx9SUGRuEhcOnzKVvNrBrabS1heqYQHljInuwLYqOeiHkLKTD/ThDe B7VxBnfkxTjKGlCSvWtm1sQuvHp6rRUs6sDuIrpwrLxR6Q+rgSzrFqr0sRHFzXoYDRk6 0nZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=M/+FiSjVkgAL1G445GEyoJEqmo9jrfjyPyoV8JOl0nQ=; b=xnPd4Dis/lPjwsyly/Hj9ZbsB2k1+c4Xt1SveJ8oC9dtcfpIgKt00akvkOBHT7E5wl OmBGo2gzApX8HFhM58fDN7ovSY/F5WP92C5v21qIBCUlUIgWPOyapOluQCh00ac9jlRb T4//jtlnTU5w9f06XHpYCrXa9mh18dgrH1dMEcJbLmY8hgffZovbHWXd5jfc6DmjJ7ql chKmzHX/MtYL5l+ygHVJpEu7VZJEuZN5+S9ubLoGaEHOSNlavDj3KUNDf7anbcC/Tmc5 7TqRc6NSpITGtgiVEPcyJiYdsRI+EORLclcXjp6Ss/eL4tUk2FcXEkbjIAv3JWXLPM/h hM6w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v24si12552067edi.341.2021.04.19.02.03.51; Mon, 19 Apr 2021 02:04:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237813AbhDSHfs (ORCPT + 99 others); Mon, 19 Apr 2021 03:35:48 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:17375 "EHLO szxga06-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237819AbhDSHfn (ORCPT ); Mon, 19 Apr 2021 03:35:43 -0400 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4FNz7b5lZCzlZ0P; Mon, 19 Apr 2021 15:33:15 +0800 (CST) Received: from [10.174.178.5] (10.174.178.5) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.498.0; Mon, 19 Apr 2021 15:35:09 +0800 Subject: Re: [PATCH v2 1/5] mm/swapfile: add percpu_ref support for swap To: "Huang, Ying" CC: , , , , , , , , , , , , References: <20210417094039.51711-1-linmiaohe@huawei.com> <20210417094039.51711-2-linmiaohe@huawei.com> <87eef7kmzw.fsf@yhuang6-desk1.ccr.corp.intel.com> <753f414f-34a1-b16a-f826-7deb2dcd4af6@huawei.com> <87czuq4uo2.fsf@yhuang6-desk1.ccr.corp.intel.com> From: Miaohe Lin Message-ID: Date: Mon, 19 Apr 2021 15:35:09 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <87czuq4uo2.fsf@yhuang6-desk1.ccr.corp.intel.com> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.178.5] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/4/19 15:09, Huang, Ying wrote: > Miaohe Lin writes: > >> On 2021/4/19 10:48, Huang, Ying wrote: >>> Miaohe Lin writes: >>> >>>> We will use percpu-refcount to serialize against concurrent swapoff. This >>>> patch adds the percpu_ref support for swap. >>>> >>>> Signed-off-by: Miaohe Lin >>>> --- >>>> include/linux/swap.h | 3 +++ >>>> mm/swapfile.c | 33 +++++++++++++++++++++++++++++---- >>>> 2 files changed, 32 insertions(+), 4 deletions(-) >>>> >>>> diff --git a/include/linux/swap.h b/include/linux/swap.h >>>> index 144727041e78..8be36eb58b7a 100644 >>>> --- a/include/linux/swap.h >>>> +++ b/include/linux/swap.h >>>> @@ -240,6 +240,7 @@ struct swap_cluster_list { >>>> * The in-memory structure used to track swap areas. >>>> */ >>>> struct swap_info_struct { >>>> + struct percpu_ref users; /* serialization against concurrent swapoff */ >>> >>> The comments aren't general enough. We use this to check whether the >>> swap device has been fully initialized, etc. May be something as below? >>> >>> /* indicate and keep swap device valid */ >> >> Looks good. >> >>> >>>> unsigned long flags; /* SWP_USED etc: see above */ >>>> signed short prio; /* swap priority of this type */ >>>> struct plist_node list; /* entry in swap_active_head */ >>>> @@ -260,6 +261,8 @@ struct swap_info_struct { >>>> struct block_device *bdev; /* swap device or bdev of swap file */ >>>> struct file *swap_file; /* seldom referenced */ >>>> unsigned int old_block_size; /* seldom referenced */ >>>> + bool ref_initialized; /* seldom referenced */ >>>> + struct completion comp; /* seldom referenced */ >>>> #ifdef CONFIG_FRONTSWAP >>>> unsigned long *frontswap_map; /* frontswap in-use, one bit per page */ >>>> atomic_t frontswap_pages; /* frontswap pages in-use counter */ >>>> diff --git a/mm/swapfile.c b/mm/swapfile.c >>>> index 149e77454e3c..66515a3a2824 100644 >>>> --- a/mm/swapfile.c >>>> +++ b/mm/swapfile.c >>>> @@ -39,6 +39,7 @@ >>>> #include >>>> #include >>>> #include >>>> +#include >>>> >>>> #include >>>> #include >>>> @@ -511,6 +512,14 @@ static void swap_discard_work(struct work_struct *work) >>>> spin_unlock(&si->lock); >>>> } >>>> >>>> +static void swap_users_ref_free(struct percpu_ref *ref) >>>> +{ >>>> + struct swap_info_struct *si; >>>> + >>>> + si = container_of(ref, struct swap_info_struct, users); >>>> + complete(&si->comp); >>>> +} >>>> + >>>> static void alloc_cluster(struct swap_info_struct *si, unsigned long idx) >>>> { >>>> struct swap_cluster_info *ci = si->cluster_info; >>>> @@ -2500,7 +2509,7 @@ static void enable_swap_info(struct swap_info_struct *p, int prio, >>>> * Guarantee swap_map, cluster_info, etc. fields are valid >>>> * between get/put_swap_device() if SWP_VALID bit is set >>>> */ >>>> - synchronize_rcu(); >>> >>> You cannot remove this without changing get/put_swap_device(). It's >>> better to squash at least PATCH 1-2. >> >> Will squash PATCH 1-2. Thanks. >> >>> >>>> + percpu_ref_resurrect(&p->users); >>>> spin_lock(&swap_lock); >>>> spin_lock(&p->lock); >>>> _enable_swap_info(p); >>>> @@ -2621,11 +2630,18 @@ SYSCALL_DEFINE1(swapoff, const char __user *, specialfile) >>>> p->flags &= ~SWP_VALID; /* mark swap device as invalid */ >>>> spin_unlock(&p->lock); >>>> spin_unlock(&swap_lock); >>>> + >>>> + percpu_ref_kill(&p->users); >>>> /* >>>> - * wait for swap operations protected by get/put_swap_device() >>>> - * to complete >>>> + * We need synchronize_rcu() here to protect the accessing >>>> + * to the swap cache data structure. >>>> */ >>>> synchronize_rcu(); >>>> + /* >>>> + * Wait for swap operations protected by get/put_swap_device() >>>> + * to complete. >>>> + */ >>> >>> I think the comments (after some revision) can be moved before >>> percpu_ref_kill(). The synchronize_rcu() comments can be merged. >>> >> >> Ok. >> >>>> + wait_for_completion(&p->comp); >>>> >>>> flush_work(&p->discard_work); >>>> >>>> @@ -3132,7 +3148,7 @@ static bool swap_discardable(struct swap_info_struct *si) >>>> SYSCALL_DEFINE2(swapon, const char __user *, specialfile, int, swap_flags) >>>> { >>>> struct swap_info_struct *p; >>>> - struct filename *name; >>>> + struct filename *name = NULL; >>>> struct file *swap_file = NULL; >>>> struct address_space *mapping; >>>> int prio; >>>> @@ -3163,6 +3179,15 @@ SYSCALL_DEFINE2(swapon, const char __user *, specialfile, int, swap_flags) >>>> >>>> INIT_WORK(&p->discard_work, swap_discard_work); >>>> >>>> + if (!p->ref_initialized) { >>> >>> I don't think it's necessary to add another flag p->ref_initialized. We >>> can distinguish newly allocated and reused swap_info_struct in alloc_swap_info(). >>> >> >> If newly allocated swap_info_struct failed to init percpu_ref, it will be considered as >> a reused one in alloc_swap_info() _but_ the field users of swap_info_struct is actually >> uninitialized. Does this make sense for you? > > We can call percpu_ref_init() just after kvzalloc() in alloc_swap_info(). > Yes, we can do it this way. But using ref_initialized might make the code more straightforward and simple? > Best Regards, > Huang, Ying > >> Many Thanks for quick review. >> >>> Best Regards, >>> Huang, Ying >>> >>>> + error = percpu_ref_init(&p->users, swap_users_ref_free, >>>> + PERCPU_REF_INIT_DEAD, GFP_KERNEL); >>>> + if (unlikely(error)) >>>> + goto bad_swap; >>>> + init_completion(&p->comp); >>>> + p->ref_initialized = true; >>>> + } >>>> + >>>> name = getname(specialfile); >>>> if (IS_ERR(name)) { >>>> error = PTR_ERR(name); >>> . >>> > . >