From: Mark Knecht <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Please suggest settings and flags in /etc/make.conf?
Date: Fri, 22 Jan 2010 05:27:49 -0800 [thread overview]
Message-ID: <5bdc1c8b1001220527s631a794cxb0dec3025cb42fee@mail.gmail.com> (raw)
In-Reply-To: <4B595938.3000806@gmail.com>
On Thu, Jan 21, 2010 at 11:52 PM, Lie Ryan <lie.1296@gmail.com> wrote:
> On 01/22/10 16:26, Peter Humphrey wrote:
>> On Friday 22 January 2010 03:05:55 Lie Ryan wrote:
>>> On 01/22/10 11:44, Mark Knecht wrote:
>>
>>>> # These are the USE flags that were used in addition to what is
>>>> provided by the # profile used for building.
>>>> USE="mmx sse sse2"
>>>
>>> No one size fits all, only you can decide the best USE flags combination
>>> for your use. You probably wouldn't know the USE flags to use until you
>>> emerged some programs. Before emerging, look at the USE flags and decide
>>> whether you will need the feature activated by the flag, and whether you
>>> want to activate the USE flags globally (add here) or locally for the
>>> specific package (in /etc/portage/package.use).
>>
>>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>>>> syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good
>>>> xtopology nonstop_tsc pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2
>>>> ssse3 cx16 xtpr pdcm sse4_1 sse4_2 aes lahf_lm ida tpr_shadow vnmi
>>>> flexpriority ept vpid
>>
>> What I did recently is to go through the list of CPU flags one by one and
>> check which of them had corresponding USE flags; I set those in make.conf on
>> the assumption that, if the processor had that feature, I might as well let
>> it use it.
>>
>
> I can tell you that's actually a lot of work. A certain technology may
> be called differently in the CPU flags and in USE flags; and often even
> after activating the USE flags, you may still need to find the feature
> in kernel config. I always wished there is a website that listed the CPU
> flags with the relevant kernel config and/or USE flags.
>
>
Agreed. Not that I'm signing up for doing a lot of work but what's
involved in starting some sort of small working group to maybe put
some of that info together informally? Maybe we can come up with
something over the next few months working together that could be the
basis of such a page?
- Mark
next prev parent reply other threads:[~2010-01-22 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 0:44 [gentoo-amd64] Please suggest settings and flags in /etc/make.conf? Mark Knecht
2010-01-21 23:49 ` Juan Fco. Giordana
2010-01-22 13:25 ` Mark Knecht
2010-01-22 3:05 ` Lie Ryan
2010-01-22 4:01 ` Mark Knecht
2010-01-22 8:02 ` Lie Ryan
2010-01-22 11:45 ` [gentoo-amd64] " Duncan
2010-01-22 5:26 ` [gentoo-amd64] " Peter Humphrey
2010-01-22 7:52 ` Lie Ryan
2010-01-22 13:27 ` Mark Knecht [this message]
2010-01-22 12:49 ` [gentoo-amd64] " Duncan
2010-01-22 13:39 ` Frank Peters
2010-01-22 19:05 ` [gentoo-amd64] " Mark Knecht
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=5bdc1c8b1001220527s631a794cxb0dec3025cb42fee@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@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