[vlc-devel] [PATCH 00/14] Move VLM implementation to a module

Rémi Denis-Courmont remi at remlab.net
Wed Sep 16 17:07:25 CEST 2020


Le keskiviikkona 16. syyskuuta 2020, 11.23.50 EEST Romain Vimont a écrit :
> Hi Rémi,
> 
> On Tue, Sep 15, 2020 at 09:10:16PM +0300, Rémi Denis-Courmont wrote:
> > Le tiistaina 15. syyskuuta 2020, 20.37.32 EEST Romain Vimont a écrit :
> > > This removes a lot of VLM code (including parsing) from libvlccore.
> > 
> > What is the actual point of this?
> 
> The idea was to lighten and simplify libvlc core (the complexity being
> moved to the VLM module), and not load the VLM code in memory when VLM
> is not used (which is often the case).

If you want to de-bloat libvlccore, move the gcrypt-based update code to a 
module. With static linking that's orders of magnitude larger than any other 
core component.

> > It won't even save memory in the case that VLM is
> > not used, since it wouldn't be paged-in either way.
> 
> Hmm, I don't know.

Moving code to a module marginally increases disk and memory use due to module 
overhead. If the module is not used, it might marginally decrease memory use, 
but probably won't. And even if it does, it's a coin toss whether it'll 
actually offset the increase.

It's negligible either way.

-- 
雷米‧德尼-库尔蒙
http://www.remlab.net/





More information about the vlc-devel mailing list