Messages in this thread | | | Date | Tue, 4 May 2021 20:58:11 -0400 | From | "Theodore Ts'o" <> | Subject | Re: Very slow clang kernel config .. |
| |
On Wed, May 05, 2021 at 12:02:33AM +0200, Miguel Ojeda wrote: > On Sun, May 2, 2021 at 11:48 PM Adrian Bunk <bunk@kernel.org> wrote: > > > > Library packages in ecosystems like Go or Rust are copies of the source > > code, and when an application package is built with these "libraries" > > (might even be using LTO) this is expected to be faster than using > > shared libraries. > > Rust libraries only need to include "copies" for generics; and only > enough information to use them. Keeping the raw source code would be > one way of doing that (like C++ header-only libraries), but it is not > required. > > However, it is true that Rust does not have a stable ABI, that the > vast majority of Rust open source applications get built from source > via Cargo and that Cargo does not share artifacts in its cache.
What does this mean for enterprise distributions, like RHEL, which need to maintain a stable kernel ABI as part of their business model. I assume it means that they will need to lock down on a specific Rust compiler and Rust libraries? How painful will it be for them to get security updates (or have to do backports of security bug fixes) for 7-10 years?
- Ted
| |