From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4CBF0C4167B for ; Tue, 13 Dec 2022 18:25:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236513AbiLMSZK (ORCPT ); Tue, 13 Dec 2022 13:25:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55206 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236365AbiLMSZH (ORCPT ); Tue, 13 Dec 2022 13:25:07 -0500 Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4FD6218349 for ; Tue, 13 Dec 2022 10:25:05 -0800 (PST) Received: by mail-lf1-x12b.google.com with SMTP id j4so6401189lfk.0 for ; Tue, 13 Dec 2022 10:25:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=A+tJhcvoCftbKyLVpmqUPG0nhb05IX809QUuL/r9UEA=; b=qrFH26ie3CcCOcVrUG4vnyD2JxiozF1PVLfibl4f1kXDlIuhmemmQN1/UHh35Kpx4n Lc8vV5P0ZYFt8XEECdLw07rqRrR7aNDxBJrCRpvmIEr8KZiDZ/tORfd4sEVY4rxsc3hR Q9vufaKW5so88JHd1bcq9/5G2EfFqOhwmEyQCjM4iXKTu9KY4yFVlcgSpQ4VorK9OlU9 UUw3awdKbZ+9mVyQQRIL8dDqAEN/iYYfiaL2bU0n8PZx4TcJmzhC0t3yEJEfjmkcT9rR hTeZyPCOApxsOReJBxfN6Ni7/GxllXjY544APewKAeJ6AMK5pT5bymtXPYiQokEfdb9D 4DbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=A+tJhcvoCftbKyLVpmqUPG0nhb05IX809QUuL/r9UEA=; b=Ce5T83mHHDiNtGlYUr7B3P+9NJHnb5MnY678Bt83G2zc8mP6pzhPJMM5/paicbl18i cs7NgjfQLJ+Ju7mNkapjZN0ecEpNu53kTWpkxq2T1L514/MbOdtqFmIM+YI5OeN3cEN2 AZt6oio10GyTWpOA7rz0TC3HiYDWOZxF9eY41AH8jaihYhZPDjaGbo8ub3DdMjh47NQZ cGGdODAYtDNET25fftxj15LJuJDE448YswzWN2HbpEqUjWGBx8R/1VaaEoCobusCbdvh lfwCXpzlJWxIiJtl3pTdZvJGHFr3EmopVeBwXHiGmAlr910zuEBHz17Q/d/P+n5hrEY0 7Hcw== X-Gm-Message-State: ANoB5pnarXxjZxApfWYWha65+XW1+vQQ0POR3dt773oOYNsaa76X5sBa kxd8800xwgtkXCNUiGOctB2b4iX6Ye1TpyCHRaH1Bg== X-Google-Smtp-Source: AA0mqf54fWx+JdQpRsJbmZbNpAXNZNETXGzEuYrCQKr+l5J/l0Hn98WboIS4WiDW1e5CD8EA0vSS10ThteIZl6a4YbM= X-Received: by 2002:a05:6512:3a86:b0:4b6:ec97:a621 with SMTP id q6-20020a0565123a8600b004b6ec97a621mr400080lfu.622.1670955903363; Tue, 13 Dec 2022 10:25:03 -0800 (PST) MIME-Version: 1.0 References: <20221212210547.1105894-1-posk@google.com> In-Reply-To: From: Peter Oskolkov Date: Tue, 13 Dec 2022 10:24:51 -0800 Message-ID: Subject: Re: [PATCH 31/31] sched_ext: Add a rust userspace hybrid example scheduler To: Peter Zijlstra Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org, brho@google.com, bristot@redhat.com, bsegall@google.com, daniel@iogearbox.net, derkling@google.com, dietmar.eggemann@arm.com, dschatzberg@meta.com, dskarlat@cs.cmu.edu, dvernet@meta.com, haoluo@google.com, joshdon@google.com, juri.lelli@redhat.com, kernel-team@meta.com, linux-kernel@vger.kernel.org, martin.lau@kernel.org, mgorman@suse.de, mingo@redhat.com, pjt@google.com, riel@surriel.com, rostedt@goodmis.org, tj@kernel.org, torvalds@linux-foundation.org, vincent.guittot@linaro.org, vschneid@redhat.com, posk@posk.io Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 13, 2022 at 3:10 AM Peter Zijlstra wrote: > > On Mon, Dec 12, 2022 at 01:05:47PM -0800, Peter Oskolkov wrote: > > Peter Zijlstra wrote: > > > > > I long for the UMCG patches -- that > > > at least was somewhat sane and trivially composes, unlike all this > > > madness. > > > > A surprise, to be sure, but a welcome one! > > Well, I did somewhat like it as I put significant effort into it. In > fact I was >.< near to merging the lot when you changed your mind and > went the syscall route. Yes, we are doing it via syscalls now, as managing pinned pages in the TLS approach seemed ... excessive? Complicated? Not sure how to describe it. But if you believe the TLS approach is sound, feel free to merge it, and we will make it work on our side. :) (Tejun, my apologies for hijacking your thread a bit...) [...]