Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp566431ybl; Mon, 12 Aug 2019 22:27:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqwTnmfDykMkGYTSKSoLa/Fk3CZ1uXpLyeilK5zKZiCyE5nK7/goRQHu0nPokT6cPJxI1E3j X-Received: by 2002:a62:ed10:: with SMTP id u16mr22028199pfh.179.1565674063068; Mon, 12 Aug 2019 22:27:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565674063; cv=none; d=google.com; s=arc-20160816; b=ZlUWhbnw4XjiQ3NQK5/kfhpjpvRek4jzCcbEdkiiQSlr+6aXF9RRi3Xzyc1kNIzkzd 8E9dLsxsYdoUfV1W2cxuN1p0CGgG7LBlSJ/v3PyzBxukSIYkpEiyfUBLtU60HEYG0w95 7Zpr6v90s2t1+TGndGOqPF9fHrj4SUEcMyuB6uDWxs72byspLsf2ierSUGT3Gy6x4DUf kieGMTMmjWPQV28Ee7YxrHM6WiDXoF+EnFrm/QZqTpfs+7zU6w5uJ44wNQxkETlQ5If+ C2Pfn94FKNVhvtdvXVlpws/SdXEK347+qXone/5EDlkbCSLQ5U7lzidSKT+kgC+1oUnj 1PFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:message-id :subject:cc:to:from:date; bh=2cZGG5YWdHPZ1xqoaelJL5x4ULjDzV1LVP7PXazb1nA=; b=yvF850WOdxLPB/LI68NYLS4v8XeMu2EjWlwQbrDXo4uJKa4yjXcGLGWmSKtbc1Jk3e 1xXchpm13wMVYo/wxor2bzgA3TYYoc0F1u8RN9W+keZW1L9oXOeM4BlNRkhM6VjlFTjO 64LQWIkr6+begjstKzSK1BdM2pAyGhcdgMngty8pnpGjf1D5pkvGtzlnWUcZjb4QGKAD XEPaIbuWkVaPUNwPlXNgMNIMIpmfrI0m5Cs6ydOKwkiNsBA2MQS+1E6Wd/p6WwewYq6O qTGLDgSkl9Bro359Qyuo1dGA7pmsmXKYxE510+8AuJpn/3LowCDaGvO0aXtJVP+UtC+T uGhg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x20si269913pjt.50.2019.08.12.22.27.27; Mon, 12 Aug 2019 22:27:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726935AbfHMF0A (ORCPT + 99 others); Tue, 13 Aug 2019 01:26:00 -0400 Received: from mga03.intel.com ([134.134.136.65]:47278 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726769AbfHMF0A (ORCPT ); Tue, 13 Aug 2019 01:26:00 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Aug 2019 22:25:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,380,1559545200"; d="scan'208";a="376185850" Received: from richard.sh.intel.com (HELO localhost) ([10.239.159.54]) by fmsmga006.fm.intel.com with ESMTP; 12 Aug 2019 22:25:59 -0700 Date: Tue, 13 Aug 2019 13:25:34 +0800 From: Wei Yang To: Matthew Wilcox Cc: Wei Yang , akpm@linux-foundation.org, mgorman@techsingularity.net, vbabka@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm/mmap.c: rb_parent is not necessary in __vma_link_list Message-ID: <20190813052534.GA17131@richard> Reply-To: Wei Yang References: <20190813032656.16625-1-richardw.yang@linux.intel.com> <20190813033958.GB5307@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190813033958.GB5307@bombadil.infradead.org> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 12, 2019 at 08:39:58PM -0700, Matthew Wilcox wrote: >On Tue, Aug 13, 2019 at 11:26:56AM +0800, Wei Yang wrote: >> Now we use rb_parent to get next, while this is not necessary. >> >> When prev is NULL, this means vma should be the first element in the >> list. Then next should be current first one (mm->mmap), no matter >> whether we have parent or not. >> >> After removing it, the code shows the beauty of symmetry. > >Uhh ... did you test this? > I reboot successfully with this patch. >> @@ -273,12 +273,8 @@ void __vma_link_list(struct mm_struct *mm, struct vm_area_struct *vma, >> next = prev->vm_next; >> prev->vm_next = vma; >> } else { >> + next = mm->mmap; >> mm->mmap = vma; >> - if (rb_parent) >> - next = rb_entry(rb_parent, >> - struct vm_area_struct, vm_rb); >> - else >> - next = NULL; >> } > >The full context is: > > if (prev) { > next = prev->vm_next; > prev->vm_next = vma; > } else { > mm->mmap = vma; > if (rb_parent) > next = rb_entry(rb_parent, > struct vm_area_struct, vm_rb); > else > next = NULL; > } > >Let's imagine we have a small tree with three ranges in it. > >A: 5-7 >B: 8-10 >C: 11-13 > >I would imagine an rbtree for this case has B at the top with A >to its left and B to its right. > >Now we're going to add range D at 3-4. 'next' should clearly be range A. >It will have NULL prev. Your code is going to make 'B' next, not A. >Right? mm->mmap is not the rb_root. mm->mmap is the first element in the ordered list, if my understanding is correct. -- Wei Yang Help you, Help me