On 19 Sep, Samuel Greear wrote:
> After looking over the gogo code it seems that they have pretty much done
> away with lame_global_flags and lame_internal_flags, and after some toying
> it seems that this is pretty much the only way to get any real performance
> out of a threaded backend. Seeing as pretty much everything has its fingers
> into those global structures it looks to be no small task. If there's an
> elegant solution, I have yet to see it, and don't really have the time with
> work and all to undertake a major renovation of the library. If someone with
> intimate knowledge of the library came up with a plan of attack I'd be willing
> to help, however.
Read only parts of the structures are no problem, you have just to make
sure, parts which can change multiple times (instead only once at
initialisation) are propperly protected (you didn't want to read from
variables which can't be updated with an atomic operation without a
protection (mutex)). Try to seperate these from the write once read many
parts of the structs (I thinks this is the difficult part).
Bye,
Alexander.
--
If Bill Gates had a dime for every time a Windows box crashed...
...Oh, wait a minute, he already does.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
--
MP3 ENCODER mailing list archive is at:
http://www.mail-archive.com/mp3encoder%40minnie.cs.adfa.edu.au/
