From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Guddla Rupesh <rupeshforu3@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Exporting cpu instruction set to kernel .config file
Date: Thu, 03 Mar 2022 18:06:56 -0500 [thread overview]
Message-ID: <128430.1646348816@turing-police> (raw)
In-Reply-To: <CAOJioufC3sLT0h=wszHzD8kgwdNbz4JShD4PHDUdT+nuVYvCPA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 595 bytes --]
On Thu, 03 Mar 2022 20:51:09 +0530, Guddla Rupesh said:
> Finally my request is there any way to export instruct set of my cpu to the
> kernel configuration and so after compilation my video encoding takes less
> time than previous.
Why would the instruction set used by the kernel matter, when video encoding
is done in userspace? You would get more improvement if you recompiled
the software that does the video encoding - and as I mentioned, it won't help
unless the compiler knows about the opcodes *and* can recognize the spots
in the userspace code where those opcodes would be useful.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2022-03-03 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 16:57 Exporting cpu instruction set to kernel .config file Guddla Rupesh
2022-03-03 1:05 ` FMDF
2022-03-03 1:20 ` FMDF
2022-03-03 15:21 ` Guddla Rupesh
[not found] ` <CAPj211vBPjs-rAHtjkQetzoOChHhaaPATBFfXNTmmnG0sGovVQ@mail.gmail.com>
2022-03-03 18:44 ` FMDF
2022-03-03 18:46 ` Fwd: " FMDF
2022-03-03 23:06 ` Valdis Klētnieks [this message]
[not found] ` <CALgyNi2MGdmjGzVnBQ+cnCg94-k3ZTeHpCik2D7HwBVtFbLLjA@mail.gmail.com>
2022-03-03 19:39 ` FMDF
2022-03-04 0:52 ` Rogério Valentim Feitoza da Silva
2022-03-04 11:18 ` Torin Carey
-- strict thread matches above, loose matches on Subject: below --
2022-03-02 17:11 Torin Carey
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=128430.1646348816@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=rupeshforu3@gmail.com \
/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