public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext"
Date: Wed, 27 May 2009 13:14:12 +0100	[thread overview]
Message-ID: <F5E4669A-6724-4E28-9BB7-61BA06A91A84@stellar.eclipse.co.uk> (raw)
In-Reply-To: <20090527130041.214f5aa9@ilievnet.com>


On 27 May 2009, at 11:00, Daniel Iliev wrote:
> ...
> I'm afraid the common sense says disabling the "cpudetection" USE
> flag could lead to the problem I described in my previous message.
> Please, don't get me wrong - I'm not arguing and I've never tried to
> build mplayer with EIS that is unsupported by the CPU. It may work if
> the build system detects and corrects such errors when cpudetection is
> disabled.

I think it shouldn't apply to mplayer, as explained by Volker earlier  
in the thread. If a USE for an unsupported EIS is detected, the  
mplayer build process will ignore it, and build without them. This is  
because mplayer specifically is particularly clever about this,  
apparently.

> I personally set the correct EIS USE flags for my CPU globally and
> disable the cpudetection flag.

Clearly this is the ideal way.

> ... I didn't suggest you this approach because I believe somewhere  
> in this
> thread you mentioned you wanted to use the same settings on several
> different systems.

Not necessarily, but I don't want to have to *think* too much about  
hardware. I mean, I can safely set MMX because I know reasonably well  
what it is, I remember when it came out, and I remember reading as the  
next couple of subsequent generations of CPU were released that they  
would continue to support it. I have a pretty good idea that MMX is  
ubiquitous, and I imagine it to be supported even to the very latest  
Intel CPUs (not sure about AMD?).

But I don't know what SSE is or SSSE (??) or any of the others, and I  
don't really have any desire to know. Just so long as my server works  
then I'm happy. I mean, I guess if I used Linux on the desktop then  
performance might be more important to me, and it would behove me to  
optimise each system. Or if my server carried a lot of load. But my  
Linux boxes mostly don't -  they sit in a corner & serve files by  
Samba & email by IMAP and very little more.

mplayer is kinda an exceptional case for me, because I rip DVDs  
to .mp4 format and then stream them across the network from the  
fileserver to my PS3. When I rip them, the process runs circa 12 or 14  
hours, so if I can shave 10% of this then that may be useful - the  
movie may be ready to watch an hour earlier, and on some occasion I  
may be glad of that.

So if I `flagedit media-video/mplayer mmx mmxext sse sse2 ssse3 3dnow  
3dnowext` that gets me the best performance for mplayer without having  
to think about it.

Of course, the amount of time I've spent on this thread, I could  
perhaps have learned *exactly* what all these extended instruction  
sets do, who designed them, whether they're cross-licensed between  
manufacturers and what their prospects are for continued support in  
the future. But I would personally find that very boring, and I am  
much happier to have learned a little about how mplayer's build system  
works and how Gentoo wraps that.

Stroller.




  reply	other threads:[~2009-05-27 12:14 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26  4:27 [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext" Stroller
2009-05-26  4:37 ` Adam Carter
2009-05-26  4:59   ` Volker Armin Hemmann
2009-05-26  4:37 ` Volker Armin Hemmann
2009-05-26  5:00   ` Stroller
2009-05-26  5:10     ` Volker Armin Hemmann
2009-05-26  6:15       ` Stroller
2009-05-26  6:27         ` Volker Armin Hemmann
2009-05-26  8:34           ` Stroller
2009-05-26 14:31     ` Daniel Iliev
2009-05-26 21:07       ` Stroller
2009-05-27  0:47         ` Daniel Iliev
2009-05-27  8:14           ` Stroller
2009-05-27 10:00             ` Daniel Iliev
2009-05-27 12:14               ` Stroller [this message]
2009-05-27 19:57                 ` Wyatt Epp
2009-05-27 20:04                   ` Volker Armin Hemmann
2009-05-27 20:09                     ` Alan McKinnon
2009-05-27 20:40                       ` Wyatt Epp
2009-05-27 20:47                         ` Volker Armin Hemmann
2009-05-27 21:04                         ` Mike Edenfield
2009-05-27 21:12                           ` Alan McKinnon
2009-05-27 23:00                       ` Adam Carter
2009-05-27 20:08                   ` Ward Poelmans
2009-05-27 21:04                     ` Mike Edenfield
2009-05-27 21:23                   ` Arttu V.
2009-05-28 10:17                     ` Daniel Iliev
2009-05-28 19:13                       ` Stroller
2009-05-28 20:08                         ` Ward Poelmans
2009-05-28 20:19                           ` Stroller
2009-05-28 20:27                             ` Ward Poelmans
2009-05-28 20:38                               ` Stroller
2009-05-29  5:30                             ` Graham Murray
2009-05-29  6:36                               ` Volker Armin Hemmann
2009-05-29  6:55                               ` Volker Armin Hemmann
2009-05-29 15:25                                 ` Mike Edenfield
2009-05-29  7:51                             ` Neil Bothwick
2009-05-26 22:20       ` KH
2009-05-26 22:26         ` KH
2009-05-26 22:32         ` Alan McKinnon
2009-05-26 13:26 ` [gentoo-user] " James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F5E4669A-6724-4E28-9BB7-61BA06A91A84@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox