From: Joshua Branson <jbranso@dismail.de>
To: Leo Famulari <leo@famulari.name>
Cc: Mark H Weaver <mhw@netris.org>, help-guix@gnu.org
Subject: Re: What processor features does Guix support on i686?
Date: Sun, 02 May 2021 18:06:41 -0400 [thread overview]
Message-ID: <87tunk4wpa.fsf@dismail.de> (raw)
In-Reply-To: <YI8TKb50etDXtZgK@jasmine.lan> (Leo Famulari's message of "Sun, 2 May 2021 17:01:29 -0400")
Leo Famulari <leo@famulari.name> writes:
> On Sun, May 02, 2021 at 12:56:45PM -0400, Joshua Branson wrote:
>> I'm kind of curious, if I were to compile my own linux kernel, and I
>> could someone select a newer processor family, would that make my kernel
>> a little more faster? Or would it just make my kernel image a little
>> smaller? Also my laptop is a Lenovo T400. So it doesn't exactly have
>> NEW features. :)
>
> Just to clarify, these kernel configuration options are for when one
> builds the kernel for "i686-linux" (Guix parlance) or "i386" (Linux
> parlance). This means 32-bit Intel-compatible.
>
> The T400 has a Core 2 Duo 64-bit procesor, so these options won't apply
> for you. That's "x86_64-linux" or "amd64", respectively.
>
> However, yes, you can build a custom kernel to eke out some performance
> improvements.
Thanks for the response! I'm not quite so interested in building a
custom kernel yet. But I think it would be cool to do one day!
--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
prev parent reply other threads:[~2021-05-02 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YI4xpDGiZdbUYkfF@jasmine.lan>
[not found] ` <87y2cxptki.fsf@netris.org>
2021-05-02 16:56 ` What processor features does Guix support on i686? Joshua Branson
2021-05-02 21:01 ` Leo Famulari
2021-05-02 22:06 ` Joshua Branson [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tunk4wpa.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
--cc=mhw@netris.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).