From: Ethan Zhao <haifeng.zhao@linux.intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Ethan Zhao <etzhao@outlook.com>,
Xin Li <xin@zytor.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: tglx@linutronix.de, dave.hansen@linux.intel.com, x86@kernel.org,
andrew.cooper3@citrix.com, mingo@redhat.com, bp@alien8.de
Subject: Re: [PATCH] x86/fred: Optimize the FRED entry by prioritizing high-probability event dispatching
Date: Fri, 17 Jan 2025 11:04:30 +0800 [thread overview]
Message-ID: <289e420d-a465-41c9-82ee-68ffbbfba0de@linux.intel.com> (raw)
In-Reply-To: <d90975a0-6b01-4a2e-92c2-2af2326e1299@zytor.com>
在 2025/1/17 9:21, H. Peter Anvin 写道:
> On 1/16/25 16:37, Ethan Zhao wrote:
>>>
>>> hpa suggested to introduce "switch_likely" for this kind of
>>> optimization
>>> on a switch statement, which is also easier to read. I measured it
>>> with
>>> a user space focus test, it does improve performance a lot. But
>>> obviously there are still a lot of work to do.
>>
>> Find a way to instruct compiler to pick the right hot branch
>> meanwhile make folks
>> reading happy... yup, a lot of work.
>>
>
> It's not that complicated, believe it or not.
>
> /*
> * switch(v) biased for speed in the case v == l
> *
> * Note: gcc is quite sensitive to the exact form of this
> * expression.
> */
> #define switch_likely(v,l) \
> switch((__typeof__(v))__builtin_expect((v),(l)))
>
I know we could play such trick for one branch, never think of there are
2-3 branches
are expected among 7 branches. :) , --- external interrupts, syscall,
page fault.
Thanks,
Ethan
> -hpa
>
--
"firm, enduring, strong, and long-lived"
next prev parent reply other threads:[~2025-01-17 3:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 6:51 [PATCH] x86/fred: Optimize the FRED entry by prioritizing high-probability event dispatching Ethan Zhao
2025-01-16 6:59 ` kernel test robot
2025-01-16 7:27 ` Xin Li
2025-01-16 9:22 ` Ethan Zhao
2025-01-16 13:03 ` Ethan Zhao
2025-01-16 13:48 ` Xin Li
2025-01-17 0:37 ` Ethan Zhao
2025-01-17 1:21 ` H. Peter Anvin
2025-01-17 3:04 ` Ethan Zhao [this message]
2025-01-17 4:19 ` Ethan Zhao
2025-01-17 4:43 ` Xin Li
2025-01-17 5:18 ` Ethan Zhao
2025-01-17 5:54 ` Xin Li
2025-01-17 6:58 ` Ethan Zhao
2025-01-17 16:17 ` H. Peter Anvin
2025-01-17 16:23 ` H. Peter Anvin
2025-01-18 4:00 ` Ethan Zhao
2025-01-17 16:24 ` H. Peter Anvin
2025-01-18 3:29 ` Ethan Zhao
2025-01-18 3:41 ` H. Peter Anvin
2025-01-18 4:06 ` Ethan Zhao
2025-01-18 4:09 ` H. Peter Anvin
2025-01-18 5:55 ` Ethan Zhao
2025-01-18 4:14 ` H. Peter Anvin
2025-01-18 6:02 ` Ethan Zhao
2025-01-16 15:08 ` Nikolay Borisov
2025-01-16 18:45 ` Xin Li
2025-01-17 0:40 ` Ethan Zhao
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=289e420d-a465-41c9-82ee-68ffbbfba0de@linux.intel.com \
--to=haifeng.zhao@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=etzhao@outlook.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.