[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190702210933.GB1506@brightrain.aerifal.cx>
Date: Tue, 2 Jul 2019 17:09:33 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Revisiting 64-bit time_t
On Tue, Jul 02, 2019 at 11:35:25AM +0200, Arnd Bergmann wrote:
> On Mon, Jul 1, 2019 at 6:08 PM Rich Felker <dalias@...c.org> wrote:
> >
> > On Mon, Jul 01, 2019 at 04:41:51PM +0200, Arnd Bergmann wrote:
> > > c) Keep backwards compatibility in libraries, but convert the
> > > distro one package at a time.
> > > Advantage: If done right, users can upgrade over rolling
> > > releases without ABIs breaking
> > > Disadvantage: very hard to get right, and much more work
> > > than the other two.
> >
> > I'm confused how "convert the distro one package at a time" comes up.
> > The only packages potentially affected are ones that provide or
> > consume a non-libc API with time_t or derived types as inputs or
> > outputs. Such providers and consumers would have to be updated in sync
> > with each other, but otherwise there should be no constraints about
> > updating packages. I think this could be implemented with distros'
> > standard "depends on" and "conflicts with" mechanics.
>
> The difference to b) would be that one allows single package updates
> at all, within the constraints of the distro dependency system.
> Actually figuring the dependencies and documenting them is most of
> the work here.
>
> > > unrelated reasons. Debian will probably want c), but might also
> > > be convinced to replace the existing 32-bit ports with musl based
> > > ones to avoid the effort and reduce RAM usage at the same
> > > time ;-)
> >
> > Replacing libc is like the polar opposite of option (c) here... :-)
>
> Correct, this would basically put debian-i386 and debian-armhf into
> category a), and create a new debian-musl-386 and debian-musl-armhf
> that starts out with time64, and have these maintained in parallel
> for as long as there is demand for both.
>
> One reason why this may be interesting is that it reduces the
> impact on the 64-bit Debian ports, which don't have to go through
> the pain of a rebuild with new package versions and dependencies
> when the actual ABI never changes for them.
>
> It depends a bit on what approach Debian chooses for upgrading
> some of the key packages, but if they determine that e.g. libcurl,
> libssl, libgtk, libpng and libreadline would all need a new soname
> for their library because of unfixable ABI incompatibility, *and* they
> want to keep the soname the same between 32 and 64 bit at all cost,
> then a new incompatible distro port can be the easier way out.
> (it's clearly too early to know what it will take to rebuild 32-bit
> debian fro time64, but we an think about the possible alternatives).
I don't think using musl instead of glibc is a viable choice for
Debian archs; there are fundamental differences in behavior that would
break things for users who don't expect the change, and software
that's explicitly glibc-only like systemd that they use and would have
to fight with. If they want to take on these fights, I'd love it, but
I wouldn't expect it to happen.
> Side question for this: do you have an estimate of the potential
> RAM saving when comparing glibc with musl builds of the same
> software?
It will be highly dependent on the software and processes running.
musl makes significant gains for lots of instances of small programs,
where the minimal glibc bloat will dominate the overall process size,
and possibly for multithreaded processes where glibc's large default
thread stacks, caching of exited threads' stacks for reuse, and malloc
arenas can consume a lot of memory that's nominally not in use by the
application. On the flip side, musl's malloc has fundamental problems
that can waste lots of memory under high contention. This will be
fixed in the next-gen malloc which I hope to start on sometime soon.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
