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;
From:   Roman Gushchin <guro@fb.com>
To:     "linux-mm@kvack.org" <linux-mm@kvack.org>
CC:     "linux-mm@kvack.org" <linux-mm@kvack.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Matthew Wilcox <willy@infradead.org>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH 0/3] vmalloc enhancements
Thread-Topic: [PATCH 0/3] vmalloc enhancements
Thread-Index: AQHUzUkDsg3nidi7+kWpLay4D4KtlqYjXRqA
Date:   Fri, 29 Mar 2019 22:07:47 +0000
Message-ID: <20190329220742.GA5804@tower.DHCP.thefacebook.com>
References: <20190225203037.1317-1-guro@fb.com>
In-Reply-To: <20190225203037.1317-1-guro@fb.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2620:10d:c090:200::2:8655]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f667cef1-1b49-444b-690a-08d6b492fa51
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020);SRVR:BYAPR15MB2293;
x-ms-traffictypediagnostic: BYAPR15MB2293:
x-microsoft-antispam-prvs: <BYAPR15MB2293C933FD119A9FB9B38211BE5A0@BYAPR15MB2293.namprd15.prod.outlook.com>
x-forefront-prvs: 0991CAB7B3
x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(39860400002)(136003)(346002)(376002)(366004)(396003)(199004)(189003)(2906002)(14454004)(5660300002)(478600001)(105586002)(106356001)(316002)(6916009)(54906003)(2351001)(25786009)(46003)(305945005)(446003)(7736002)(5640700003)(1076003)(9686003)(4326008)(6512007)(71200400001)(86362001)(71190400001)(53936002)(256004)(6246003)(11346002)(476003)(229853002)(76176011)(102836004)(33656002)(6486002)(6506007)(386003)(97736004)(486006)(6436002)(186003)(8936002)(52116002)(6116002)(68736007)(99286004)(81156014)(81166006)(8676002)(2501003);DIR:OUT;SFP:1102;SCL:1;SRVR:BYAPR15MB2293;H:BYAPR15MB2631.namprd15.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:1;MX:1;
received-spf: None (protection.outlook.com: fb.com does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: W5FU7W/JiPUrK4lejOvnbwWB+y3pfS69ZTobTf6Vjyg7VAv1hpSR1f8Z7JRTlIClxNmDj8x8KpSW4d9dgEO1Fmik9CkBpj3QG5M180AODfbzhNAGJTkq22lXtoh23tZ9PK3wyB8YaozpAnnJbeDxfwreCkMcLqxGYyJCSTzgi849CDBxZGE6Vl8NE+KjgwBKS9G1EwDFYHm4dXhr/KjJz9tun7Gvy3PNOQcdGgXIEzA7pE3n0alEqZDEaPmzampMmX9bijQ+GAY5erJnGriacPi3YXU7R6zt76zex8+rTSZL8TizX5+jBMJBeQsXeM3YVGpt46H0Y6XC19aB27irrPo1dOgJt0iziwItM9EgcGRI4ui76mMngU2EsML4Kw0Tx2BMEC5FWH+2PIF5EYM83uQE4nATKeEg4VzgdpQ07fo=
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9E26A1FD2CD4644A901615B7C770360C@namprd15.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f667cef1-1b49-444b-690a-08d6b492fa51
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Mar 2019 22:07:47.9879
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2293
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-29_13:,,
 signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Feb 25, 2019 at 12:30:34PM -0800, Roman Gushchin wrote:
> The patchset contains few changes to the vmalloc code, which are
> leading to some performance gains and code simplification.
>=20
> Also, it exports a number of pages, used by vmalloc(),
> in /proc/meminfo.
>=20
> Patch (1) removes some redundancy on __vunmap().
> Patch (2) separates memory allocation and data initialization
>   in alloc_vmap_area()
> Patch (3) adds vmalloc counter to /proc/meminfo.
>=20
> v3->v2:
>   - switched back to atomic after more accurate perf measurements:
>   no visible perf difference
>   - added perf stacktraces in commmit message of (1)
>=20
> v2->v1:
>   - rebased on top of current mm tree
>   - switch from atomic to percpu vmalloc page counter
>=20
> RFC->v1:
>   - removed bogus empty lines (suggested by Matthew Wilcox)
>   - made nr_vmalloc_pages static (suggested by Matthew Wilcox)
>   - dropped patch 3 from RFC patchset, will post later with
>   some other changes
>   - dropped RFC
>=20
> Roman Gushchin (3):
>   mm: refactor __vunmap() to avoid duplicated call to find_vm_area()
>   mm: separate memory allocation and actual work in alloc_vmap_area()
>   mm: show number of vmalloc pages in /proc/meminfo
>=20
>  fs/proc/meminfo.c       |   2 +-
>  include/linux/vmalloc.h |   2 +
>  mm/vmalloc.c            | 107 ++++++++++++++++++++++++++--------------
>  3 files changed, 73 insertions(+), 38 deletions(-)
>=20
> --=20
> 2.20.1
>=20

Ping. Any comments/suggestions/objections?

Thanks!