Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk
On Tuesday 30 October 2001 02:52 pm, you wrote:
> > One possiiblity: IIRC, if you do an strace of a progrma using the dynamic
> > linker using say, libfoo, it will be checking for something like
> > i686/mmx/libfoo, i686/libfoo first..Perhaps this can be used?
>
> Sorry, too much technical for me :-(
OK, let's clarify. Here is a pasting of the strace (system call log), for a
program:
open("/usr/lib/qt2/lib/libICE.so.6", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("i686/mmx/libICE.so.6", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("i686/libICE.so.6", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("mmx/libICE.so.6", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("libICE.so.6", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/X11R6/lib/libICE.so.6", O_RDONLY) = 3
THis is the linked trying to open a library. Notice that the linked is trying
to load an i686/MMX optimized version of the library first, although not in
particularly nice places (looks like a relative dir from here).
This might be useful for packaing, if one simply includes multiples copies of
performance-sensitive libraries, such as avifile, and let's ld.so pick the
right one. Unfortunatel,y this probably doesn't work for dlopen()'ed
libraries.
Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk
Guys, P1's slower than 166Mhz do not allow MMX-enabled multimedia programs to run. My P1 166 is that way. Matthew - Original Message - From: "David Walluck" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 30, 2001 8:15 PM Subject: Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk > On Tue, 30 Oct 2001, Brian J. Murrell wrote: > > > I agree. Turn MMX on on all of your multi-media builds! :-) > > It is safe to turn MMX on. Original P1's do not support it, but I believe > it will run. Of course, as mentioned, a P1 is very slow to be running > video on, but that's not an excuse to exclude it, but as I said, I believe > MMX optimizations are safe. The K6 supports MMX as well. > > -- > Sincerely, > > David Walluck > <[EMAIL PROTECTED]> > >
Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk
On Tue, 30 Oct 2001, Brian J. Murrell wrote: > I agree. Turn MMX on on all of your multi-media builds! :-) It is safe to turn MMX on. Original P1's do not support it, but I believe it will run. Of course, as mentioned, a P1 is very slow to be running video on, but that's not an excuse to exclude it, but as I said, I believe MMX optimizations are safe. The K6 supports MMX as well. -- Sincerely, David Walluck <[EMAIL PROTECTED]>
Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk
> Sure. AFAIK (please correct me if i'm wrong): > sse -> pentium III only > 3dnow -> amd K6 only > 3dnowex -> amd K7 (athlon) only > mmx -> all recent computer > mmx2 -> ?? > Sofar, the most reasonable performance/maintainance tradeoff seems to > maintain this set of package: > - i586 with no optimization at all > - i686 with mmx optimization > sse is also pIV and AthlonXP > > One possiiblity: IIRC, if you do an strace of a progrma using the dynamic > > linker using say, libfoo, it will be checking for something like > > i686/mmx/libfoo, i686/libfoo first..Perhaps this can be used? > Sorry, too much technical for me :-( > -- > Guillaume Rousse <[EMAIL PROTECTED]> > GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html >
Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk
Ainsi parlait Maksim Orlovich : > On Tue, 30 Oct 2001, Oden Eriksson wrote: > > On Tuesdayen den 30 October 2001 17.44, Brian J. Murrell wrote: > > > On Tue, Oct 30, 2001 at 05:27:52PM +0100, Guillaume Rousse wrote: > > > > mplayer currently support mmx, mmx2, 3dnow, 3dnowex and sse > > > > optimisations. Turning them all is not a good solution, and i'm not > > > > sure which one one would correspond to a 'reasonable' subset: mmx + > > > > 3dnow + sse ? > > > > > > Of course I vote for whatever optimization Athlon's have in them. MMX > > > and 3dnow I think. :-) Anything else for an Athlon? > > > > one must ask himself what differencies/benefits/drawbacks all these > > options bring, it just might be enough with mmx only? Sure. AFAIK (please correct me if i'm wrong): sse -> pentium III only 3dnow -> amd K6 only 3dnowex -> amd K7 (athlon) only mmx -> all recent computer mmx2 -> ?? Sofar, the most reasonable performance/maintainance tradeoff seems to maintain this set of package: - i586 with no optimization at all - i686 with mmx optimization > One possiiblity: IIRC, if you do an strace of a progrma using the dynamic > linker using say, libfoo, it will be checking for something like > i686/mmx/libfoo, i686/libfoo first..Perhaps this can be used? Sorry, too much technical for me :-( -- Guillaume Rousse <[EMAIL PROTECTED]> GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html
Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk
On Tue, 30 Oct 2001, Oden Eriksson wrote: > On Tuesdayen den 30 October 2001 17.44, Brian J. Murrell wrote: > > On Tue, Oct 30, 2001 at 05:27:52PM +0100, Guillaume Rousse wrote: > > > mplayer currently support mmx, mmx2, 3dnow, 3dnowex and sse > > > optimisations. Turning them all is not a good solution, and i'm not sure > > > which one one would correspond to a 'reasonable' subset: mmx + 3dnow + > > > sse ? > > > > Of course I vote for whatever optimization Athlon's have in them. MMX > > and 3dnow I think. :-) Anything else for an Athlon? > > one must ask himself what differencies/benefits/drawbacks all these options > bring, it just might be enough with mmx only? One possiiblity: IIRC, if you do an strace of a progrma using the dynamic linker using say, libfoo, it will be checking for something like i686/mmx/libfoo, i686/libfoo first..Perhaps this can be used?
Re: [Cooker] Re: Re: avifile-0.6.0-0.20011026.1mdk
On Tuesdayen den 30 October 2001 17.44, Brian J. Murrell wrote: > On Tue, Oct 30, 2001 at 05:27:52PM +0100, Guillaume Rousse wrote: > > mplayer currently support mmx, mmx2, 3dnow, 3dnowex and sse > > optimisations. Turning them all is not a good solution, and i'm not sure > > which one one would correspond to a 'reasonable' subset: mmx + 3dnow + > > sse ? > > Of course I vote for whatever optimization Athlon's have in them. MMX > and 3dnow I think. :-) Anything else for an Athlon? one must ask himself what differencies/benefits/drawbacks all these options bring, it just might be enough with mmx only? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Oden Eriksson, Deserve-IT Networks, Jokkmokk, Sweden. | Mandrake Linux release 8.2 (Cooker) for i586 | Current uptime with kernel 2.4.13-1mdksmp: 10:12 | cpu0 @ 814.28 bm, fan 4500 rpm, temp +36.0°C | cpu1 @ 815.92 bm, fan 4500 rpm, temp +33°C
