Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp885304ybg; Tue, 28 Jul 2020 23:37:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzofnsLgXhibBivht4tDMOl1MVu0CPQUA47rd/2WxlPaLqpjqGq/7GXuiQWBfk/gE0IFMW1 X-Received: by 2002:a17:906:6004:: with SMTP id o4mr20889703ejj.411.1596004631912; Tue, 28 Jul 2020 23:37:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596004631; cv=none; d=google.com; s=arc-20160816; b=0WXLWP9R5AXiJ8nIEJ+rCWJy8oe7OxA6qSFO/U0VR2hMP7IXHcGj4tA4AIVgiMI58d 9j8r4wJKqUji+dZkVKEjfPKiJnRMqwLL/V16zFJuxip94BdAFSx/w6lnAqSyYoLsmxJ3 TUNOczrLrMlCrMKEp9o2LyspfAuiT2TnX61rSLLB263lSBLfHycEm4F7PzgWzGIdbcRh Ad0h4uB3RnsbSir0bwHTnVKaiJamDlh90azFQ1P1fxCXyBrC6Q+BHrQVIFyIO/pa+Z/u gv1kIzRhrOfnxMFMVjATwIpwRlP8YFqRln6LYt+zOg3WYRimzUq4YMcISbE9H8BhBp4E NmJw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=XIlV4Q6P2hxyTbpTmIfkxHinx5NVBW4nTQ0DNENriYg=; b=UmttyaW1GvXk5ekwn+hVy3rCb0fw4Sh+/69AaFtE7OUqQULRn9TPPUoNT4dh5Z/3Gk TRUIVLH2ZYnOKSvqxl/GE9g689ASracjbMXDVHJZeMqTkCJzqk89W3fpmEUADAPuocBg kFUFgubI+RNIe/XJkjg4d9rw4/PEGz5DRr3Em8lXdIitnxGb7ZqzMbw/Jj5eCgdcQ676 Rky08MOT5XIf7nBJmCsQesKUPDdevYN4yw4rIkKNQangIY+dZWfcYIbRoq9KlbGyKm9z K6hFtq3V3sfSZm7cOfRPcpfIsDA2R9MbFHbYRLHApUdeOOiii0vodHjPxZZvCxfV3Hsn nsuw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k17si507136eji.304.2020.07.28.23.36.48; Tue, 28 Jul 2020 23:37:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726536AbgG2Gea (ORCPT + 99 others); Wed, 29 Jul 2020 02:34:30 -0400 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:59943 "EHLO relay1-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726314AbgG2Gea (ORCPT ); Wed, 29 Jul 2020 02:34:30 -0400 X-Originating-IP: 50.39.163.217 Received: from localhost (50-39-163-217.bvtn.or.frontiernet.net [50.39.163.217]) (Authenticated sender: josh@joshtriplett.org) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id E3C58240003; Wed, 29 Jul 2020 06:34:20 +0000 (UTC) Date: Tue, 28 Jul 2020 23:34:17 -0700 From: Josh Triplett To: Pavel Machek Cc: Linus Torvalds , Christian Brauner , Nick Desaulniers , alex.gaynor@gmail.com, Greg KH , geofft@ldpreload.com, jbaublitz@redhat.com, Masahiro Yamada , Miguel Ojeda , Steven Rostedt , LKML , clang-built-linux , Kees Cook Subject: Re: Linux kernel in-tree Rust support Message-ID: <20200729063417.GD286933@localhost> References: <20200710062803.GA1071395@kroah.com> <20200710125022.alry7wkymalmv3ge@wittgenstein> <20200710225934.GA16881@localhost> <20200711210317.GA60425@localhost> <20200728204037.GC1012@bug> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200728204037.GC1012@bug> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 28, 2020 at 10:40:38PM +0200, Pavel Machek wrote: > > We just need to make sure that any kernel CI infrastructure tests that > > right away, then, so that failures don't get introduced by a patch from > > someone without a Rust toolchain and not noticed until someone with a > > Rust toolchain tests it. > > So... I'm fan of Rust, but while trying to use it one thing was obvious: it > takes _significantly_ longer than C to compile and needs gigabyte a lot of RAM. > > Kernel is quite big project, can CI infrastructure handle additional load? > > Will developers see significantly longer compile times when Rust is widespread? I wouldn't expect the addition of Rust to the kernel to substantially impact overall build time; on balance, I'd expect the major bottleneck in kernel builds to continue to be linking and other serialized steps, not compiling and other highly parallel steps. There are also *many* things that can be done to improve Rust build time in a project. And I don't expect that in-kernel Rust will have many dependencies on third-party crates (since they'd need to be checked into the tree).