[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200728204037.GC1012@bug>
Date: Tue, 28 Jul 2020 22:40:38 +0200
From: Pavel Machek <pavel@....cz>
To: Josh Triplett <josh@...htriplett.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Christian Brauner <christian.brauner@...ntu.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
alex.gaynor@...il.com, Greg KH <gregkh@...uxfoundation.org>,
geofft@...reload.com, jbaublitz@...hat.com,
Masahiro Yamada <masahiroy@...nel.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Kees Cook <keescook@...omium.org>
Subject: Re: Linux kernel in-tree Rust support
Hi!
> > No, please make it a "is rust available" automatic config option. The
> > exact same way we already do the compiler versions and check for
> > various availability of compiler flags at config time.
>
> That sounds even better, and will definitely allow for more testing.
>
> 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?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists