Received: by 10.192.165.148 with SMTP id m20csp5464529imm; Wed, 9 May 2018 05:37:57 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpKQt36GJQNAEnilBjifGKtJ9ygDmzgT14jYSDihLWNGxfZfBuhgj6jAk8/XUBSC6V89QM/ X-Received: by 10.98.130.140 with SMTP id w134mr35996818pfd.138.1525869477245; Wed, 09 May 2018 05:37:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525869477; cv=none; d=google.com; s=arc-20160816; b=YQ1FUttjq5C6aP5TmFL6Fe65Ltm7OQN223YBPisP7xHzHCXzGMFtFcxQwBUhNXwzMX 7hhxwCr4V2mRhBnyUEJOHeuJ07ERLPYZm5VO2tQuMBYtOVRwZHe03VxD5i9fPThtIppO AVa80wQ8G0tGEgh3JXw0XqNVgCf5srOr7NTKTrvsI9JfW+Oq5/2PTLILE3rKd0a9otHm 0gV3b+HJ8UFbCEov3sT98pJZzyvMyVp0WLzKG+u7nWNqNe+5fMJpI7gbbcP2KYUFFDPc fzCGDuI+JyBsZ7b0AaAgJdIZj3ATGlZawlp30zulPf92Og6n3sT5atEV78oW8wIlveLK HPeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=51g8/bUZaYmva0YywWze3fcxQJ2AgfM7+BaUNz4a+fg=; b=Yo5rErivD8TpnFBVqkltRYGyUsc9YnPYuOpVzpM+sf9rMxlJBQlQD4ehdWgD0EyPhW FdWr5EMVOd/M2XaOlBqF8bdBvF45b6CxJ19w+3Wja/UezuVGrlaV3Lwn6QpEdNswdOSt oATsQdLdrbtY4hQM6OH+5L8RRzddA22s0wpfgQn4bXruzkidgFTLJUKp201y7qthoRoQ KShfxETzURKlqIcHC04jMCQ3xXJGiLJUsX5HtEHU1L6oGzfjYUD5Ok7951rO+WvAgvW1 IvKdcY3fFmtoKucVPGnWnQXu2Aukeh+mGWxpCCioM5Q/b0AfpvaUXsf/LCmNNpLquwU4 Ev8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=rH6StJIk; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s5-v6si3231931pgv.271.2018.05.09.05.37.41; Wed, 09 May 2018 05:37:57 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=rH6StJIk; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934630AbeEIMhS (ORCPT + 99 others); Wed, 9 May 2018 08:37:18 -0400 Received: from mail-oi0-f44.google.com ([209.85.218.44]:37430 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932875AbeEIMhQ (ORCPT ); Wed, 9 May 2018 08:37:16 -0400 Received: by mail-oi0-f44.google.com with SMTP id w123-v6so22344924oia.4; Wed, 09 May 2018 05:37:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=51g8/bUZaYmva0YywWze3fcxQJ2AgfM7+BaUNz4a+fg=; b=rH6StJIkpB/asEP+SyTRTTfcfoObFf9NVDSvjjpjqhi99R4dku0Pqo5JjaavtkuqqL uZKWuDV/KwHWiFT73gaHuxh2jhuxouCZXeR1uA7x1CKP6YgY/JCAYLRiGL72K3gVa4PR m1atuH4s3sSLYH2fZ9Z4xlFL8nAkmzC84q2aXS/FhPqPrR/muPXRruQeZ58zfbNOE2Mh TGuYyMbzFY+dLBRUDG4EPQ/6ApmteQKR3Nw6KGEFI3jT0PEX8N2IMLIFLIcC5Ks+MR32 oiWbfZI9RwgLJV9ra0KU1c8sWPiE+8FhdLvGX1CaCcuH3gVtmKy0csgKnAt7muaOw2/F 8POw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=51g8/bUZaYmva0YywWze3fcxQJ2AgfM7+BaUNz4a+fg=; b=G839hymcrhCJvNvQ2dTRVyCirewjIrh+L4BgjRKiwNaCC/OLPhqOnZ/RA6ySI4g05p iWS8dVVA7SDLUQznW7NhWylTACpWh6X5531lGvyx5AabUxz2iIpdPpmhVXh9zZ7l7oMS ZGdF+0iPKgL4zu8ZL+SCWUpnRqbs9EqkptqaZ7wo31eiMogE4ZI3CSVfuUdViiALW2O+ HLC2LzvqxyRZ9b9X5xG7V0vjWBK7JyFv55kQ2otZonreQk8odDSzM4iYKfbtA5LKXR8J tUSllHntKvjqvXzP+zj65eZAVE4fCRkHdkzMR5oVGSpQxveznAHtA7iJb/d/JyOaS3Nn 3Gtg== X-Gm-Message-State: ALQs6tDqg4y0inHcVBkL9AYh9RnkP2Vpnh85BpmKte7aLf8FWCugp1m/ ReHNonMxAPHh5RxuLQ6QC9DrTuXAAF3KfZwesqs= X-Received: by 2002:aca:1216:: with SMTP id 22-v6mr29069061ois.50.1525869436475; Wed, 09 May 2018 05:37:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.201.88.68 with HTTP; Wed, 9 May 2018 05:37:16 -0700 (PDT) In-Reply-To: <20180509122454.GR32366@dhcp22.suse.cz> References: <20180411104832.GF23400@dhcp22.suse.cz> <20180509122454.GR32366@dhcp22.suse.cz> From: Ganapatrao Kulkarni Date: Wed, 9 May 2018 18:07:16 +0530 Message-ID: Subject: Re: fd3e45436660 ("ACPI / NUMA: ia64: Parse all entries of SRAT memory affinity table") To: Michal Hocko Cc: Ganapatrao Kulkarni , Tony Luck , "Rafael J. Wysocki" , tiantao6@huawei.com, LKML , linux-acpi@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Michal On Wed, May 9, 2018 at 5:54 PM, Michal Hocko wrote: > On Wed 11-04-18 12:48:32, Michal Hocko wrote: >> Hi, >> my attention was brought to the %subj commit and either I am missing >> something or the patch is quite dubious. What is it actually trying to >> fix? If a BIOS/FW provides more memblocks than the limit then we would >> get misleading numa topology (numactl -H output) but is the situation >> much better with it applied? Numa init code will refuse to init more >> memblocks than the limit and falls back to dummy_numa_init (AFAICS) >> which will break the topology again and numactl -H will have a >> misleading output anyway. IIRC, the MEMBLOCK beyond max limit getting dropped from visible memory(partial drop from a node). this patch removed any upper limit on memblocks and allowed to parse all entries of SRAT. >> >> So why is the patch an improvement at all? > > ping? I would be tempted to simply revert the patch as a wrong fix. > -- > Michal Hocko > SUSE Labs thanks Ganapat sorry, somehow, i have missed your previous email