From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f197.google.com (mail-qk0-f197.google.com [209.85.220.197]) by kanga.kvack.org (Postfix) with ESMTP id 607206B0038 for ; Tue, 19 Dec 2017 16:41:11 -0500 (EST) Received: by mail-qk0-f197.google.com with SMTP id u1so14197265qka.7 for ; Tue, 19 Dec 2017 13:41:11 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id g5sor11732719qtk.24.2017.12.19.13.41.10 for (Google Transport Security); Tue, 19 Dec 2017 13:41:10 -0800 (PST) Date: Tue, 19 Dec 2017 13:41:07 -0800 From: Tejun Heo 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: Sender: owner-linux-mm@kvack.org List-ID: 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