From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [RFC PATCH] mm: memcontrol: memory+swap accounting for cgroup-v2 Date: Tue, 19 Dec 2017 13:41:07 -0800 Message-ID: <20171219214107.GR3919388@devbig577.frc2.facebook.com> References: <20171219000131.149170-1-shakeelb@google.com> <20171219124908.GS2787@dhcp22.suse.cz> <20171219152444.GP3919388@devbig577.frc2.facebook.com> <20171219173354.GQ3919388@devbig577.frc2.facebook.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=4erIXUnqrK6JAWG//IjJJVaBj4cxfVKtubglKPxT0SM=; b=ITqLklpkhX4joS5SAYbnYqh6o0wJqfovcbV9OHQCAg1Ci9FtrN5883JfU0a3gyRfwe eOA+VyydB0I7LNIq4FuirxZpRYDcGV5bRNzsE4ts9ODG1NWqhzlNZZWMyKbppuKeGDr1 dFAkRzqo6GCh23BmtjtyvYim1nDb/0VX/CWlutJ5De1oeCjXXBsgCfjHLMTRJ+90UbWl K0CzHPW+ZGdVyhPheAiQgHy5dollFmoqlqgLpJdm1HxdU3POEQspOciZ8FU862sFZv+N K+YD5wjUPKZzTs1vKXbzrxUBw9g4AYlwhR47PoB8kOgGpLjpNaRTLJ0K0K8gIkzaU6YY zc9w== Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Shakeel Butt Cc: Michal Hocko , Li Zefan , Roman Gushchin , Vladimir Davydov , Greg Thelen , Johannes Weiner , Hugh Dickins , Andrew Morton , Linux MM , LKML , Cgroups , linux-doc@vger.kernel.org Hello, On Tue, Dec 19, 2017 at 10:25:12AM -0800, Shakeel Butt wrote: > Making the runtime environment, an invariant is very critical to make > the management of a job easier whose instances run on different > clusters across the world. Some clusters might have different type of > swaps installed while some might not have one at all and the > availability of the swap can be dynamic (i.e. swap medium outage). > > So, if users want to run multiple instances of a job across multiple > clusters, they should be able to specify the limits of their jobs > irrespective of the knowledge of cluster. The best case would be they > just submits their jobs without any config and the system figures out > the right limit and enforce that. And to figure out the right limit > and enforcing it, the consistent memory usage history and consistent > memory limit enforcement is very critical. I'm having a hard time extracting anything concrete from your explanation on why memsw is required. Can you please ELI5 with some examples? Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753535AbdLSVlR (ORCPT ); Tue, 19 Dec 2017 16:41:17 -0500 Received: from mail-qt0-f177.google.com ([209.85.216.177]:46147 "EHLO mail-qt0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752860AbdLSVlL (ORCPT ); Tue, 19 Dec 2017 16:41:11 -0500 X-Google-Smtp-Source: ACJfBos/zhpcSwPWtBZvxG+qdaU+YbZrybo8b04UcTmApLokgFfGdBK6Za5jxJ7JhCTCGV18F1AL3w== Date: Tue, 19 Dec 2017 13:41:07 -0800 From: Tejun Heo To: Shakeel Butt Cc: Michal Hocko , Li Zefan , Roman Gushchin , Vladimir Davydov , Greg Thelen , Johannes Weiner , Hugh Dickins , Andrew Morton , Linux MM , LKML , Cgroups , linux-doc@vger.kernel.org Subject: Re: [RFC PATCH] mm: memcontrol: memory+swap accounting for cgroup-v2 Message-ID: <20171219214107.GR3919388@devbig577.frc2.facebook.com> References: <20171219000131.149170-1-shakeelb@google.com> <20171219124908.GS2787@dhcp22.suse.cz> <20171219152444.GP3919388@devbig577.frc2.facebook.com> <20171219173354.GQ3919388@devbig577.frc2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Tue, Dec 19, 2017 at 10:25:12AM -0800, Shakeel Butt wrote: > Making the runtime environment, an invariant is very critical to make > the management of a job easier whose instances run on different > clusters across the world. Some clusters might have different type of > swaps installed while some might not have one at all and the > availability of the swap can be dynamic (i.e. swap medium outage). > > So, if users want to run multiple instances of a job across multiple > clusters, they should be able to specify the limits of their jobs > irrespective of the knowledge of cluster. The best case would be they > just submits their jobs without any config and the system figures out > the right limit and enforce that. And to figure out the right limit > and enforcing it, the consistent memory usage history and consistent > memory limit enforcement is very critical. I'm having a hard time extracting anything concrete from your explanation on why memsw is required. Can you please ELI5 with some examples? Thanks. -- tejun