x86_64 confusion

Kam Leo kam.leo at gmail.com
Sat Apr 7 17:44:58 UTC 2007


On 4/7/07, Jeffrey Ross <jeff at bubble.org> wrote:
> The system is running kernel (uname -a): Linux wisdom.bubble.org
> 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 18:38:39 EST 2007 x86_64 x86_64
> x86_64 GNU/Linux  and is running on a Pentium D.
>
> I was converting some avi files for use on my iPod (to load via gtkpod)
> using the following command:
>
> ffmpeg -vcodec xvid -b 300 -qmin 3 -qmax 5 -bufsize 4096 -g 300 -acodec
> aac -ab 96 -i /media/Da*/*1x13*.avi -s 320x240 -aspect 4:3 13-pdtv.mp4
>
> which responds with the following:
>
> FFmpeg version SVN-r7813, Copyright (c) 2000-2006 Fabrice Bellard, et al.
>   configuration:  --prefix=/usr --incdir=/usr/include/ffmpeg
> --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man
> --arch=x86_64 --extra-cflags=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64
> -mtune=generic --enable-mp3lame --enable-libogg --enable-libtheora
> --enable-vorbis --enable-faad --enable-faac --enable-libgsm
> --enable-xvid --enable-x264 --enable-a52 --enable-a52bin --enable-dts
> --enable-pp --disable-static --enable-shared --enable-gpl
> --disable-debug --disable-opts --disable-strip
>   libavutil version: 49.3.0
>   libavcodec version: 51.30.0
>   libavformat version: 51.8.0
>   built on Feb  4 2007 08:14:48, gcc: 4.1.1 20070105 (Red Hat 4.1.1-51)
> Input #0, avi, from '/media/Data disc (08 Jan
> 07)/Video.1x13.pdtv.dfd.xvid.avi':
>   Duration: 00:46:17.1, start: 0.000000, bitrate: 1129 kb/s
>   Stream #0.0: Video: mpeg4, yuv420p, 640x352, 25.00 fps(r)
>   Stream #0.1: Audio: mp3, 48000 Hz, stereo, 128 kb/s
> Output #0, mp4, to '13-pdtv.mp4':
>   Stream #0.0: Video: xvid, yuv420p, 320x240, q=3-5, 0 kb/s, 25.00 fps(c)
>   Stream #0.1: Audio: aac, 48000 Hz, stereo, 96 kb/s
> Stream mapping:
>   Stream #0.0 -> #0.0
>   Stream #0.1 -> #0.1
> Press [q] to stop encoding
> frame=69427 q=5.0 Lsize=  151345kB time=2777.1 bitrate= 446.4kbits/s
> video:117240kB audio:32540kB global headers:0kB muxing overhead 1.044881%
>
>
> By what I can tell everything was compiled as 64bit apps however the
> application only used one processor.  Am I not correct that a 64 bit
> application should treat the dual core as a single processor?
>
> Thanks, Jeff

No, it is the developer(s), compiler, and OS combined that determine
whether an application will take advantage of multiple processors.




More information about the fedora-list mailing list