From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal =?iso-8859-1?Q?Koutn=FD?= Subject: Re: [PATCH v6 2/6] cgroup: gpu: Add a cgroup controller for allocator attribution of GPU memory Date: Thu, 5 May 2022 13:50:15 +0200 Message-ID: <20220505115015.GD10890@blackbody.suse.cz> References: <20220502231944.3891435-1-tjmercier@google.com> <20220502231944.3891435-3-tjmercier@google.com> <20220504122558.GB24172@blackbody.suse.cz> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1651751416; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=SFH/x2L4G69sbr6PPcrJ24GF6EKzycaRm+AGvFywOyg=; b=Hi7oi4+HvgHIFy7zdrmmaaXxpCzxgIsU/9DIcQEQIsZBrzEnC99VBYyTdl9tCC5Clj0fNo S4wfHAcq5GS0FxgqjHIneVl1e76wHk0FgPIrmw1/VLSR1LTsnu6LUe2oRBxPFHVVShOMzR bOw8YBZW592ZS2VzcJD/HrayK6QgMM8= Content-Disposition: inline In-Reply-To: List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "T.J. Mercier" Cc: Tejun Heo , Zefan Li , Johannes Weiner , Daniel Vetter , Hridya Valsaraju , Christian =?iso-8859-1?Q?K=F6nig?= , John Stultz , Todd Kjos , Carlos Llamas , Suren Baghdasaryan , Kalesh Singh , Kenny.Ho-5C7GfCeVMHo@public.gmane.org, Shuah Khan , kernel-team-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Wed, May 04, 2022 at 10:19:20AM -0700, "T.J. Mercier" wrote: > Should I export these now for this series? Hehe, _I_ don't know. Depends on the likelihood this lands in and is built upon. > No, except maybe the gpucg_bucket name which I can add an accessor > function for. Won't this mean depending on LTO for potential inlining > of the functions currently implemented in the header? Yes. Also depends how much inlining here would be performance relevant. I suggested this with an OS vendor hat on, i.e. the less such ABI, the simpler. > I'm happy to make this change, but I wonder why some parts of the > kernel take this approach and others do not. I think there is no convention (see also Documentation/process/stable-api-nonsense.rst ;-)). Regards, Michal