Posts
469
Following
90
Followers
94
n00b Kernel Hacker
- Intern @ NVIDIA Korea (Security System Software) (2024.06 ~)
- Ex-Intern @ Panmneisa (CXL emulation stuff) (~2023.12)
- Undergraduate majoring CSE (estimated graduation: Feb. 2025)
- Working as reviewer at Linux Slab subsystem
- Born in August 6, 2000

Opinions are my own.

My interests are:
Memory Management,
Computer Architecture,
Circuit Design,
Virtualization
hyeyoo

Hyeonggon Yoo

Reply to @vbabka
Edited 11 months ago
@vbabka I hope no one is scared even without reading the code
0
0
1
hyeyoo

Hyeonggon Yoo

At OSS Festival last week (in Seoul)
1
0
5
hyeyoo

Hyeonggon Yoo

War and Peace
0
0
2
hyeyoo
repeated
JenMsft@mastodon.social

Jen Gentleman

How QR codes are made:

1
21
2
hyeyoo

Hyeonggon Yoo

Shared bicycles (not a biker gang)
0
0
1
hyeyoo

Hyeonggon Yoo

Reply to @hyeyoo
But (hopefully) the length of a development cycle is long enough to review/test all of them
1
0
2
hyeyoo

Hyeonggon Yoo

the number of slab patches in this cycle is quite larger than usual...
1
0
2
hyeyoo
repeated
lkundrak@metalhead.club

HAMMER SMASHED FILESYSTEM 🇺🇦

patch review process finally moving on from mailing lists

2
6
5
hyeyoo
repeated
brauner@mastodon.social

Christian Brauner 🦊🐺

Edited 11 months ago

Hey people. Last year we had the first Devroom at . And we're running the Devroom for in 2024 as well!

2024 is taking place over the weekend of the 3 & 4 February in Brussels, Belgium!

It is a wonderful event that's very close to my and a lot of people's hearts!

Join @rppt, Daniel Borkmann, and @stgraber, and myself and make this another great !

We're very excited for your submissions!

https://lists.fosdem.org/pipermail/fosdem/2023q4/003536.html

0
22
3
hyeyoo
repeated
nathanchance@fosstodon.org

Nathan Chancellor

For the 2023 ClangBuiltLinux meetup, I decided to revisit my benchmarks comparing how building LLVM with different optimizations such as LTO, PGO, and BOLT can impact how fast it can build Linux kernels:

https://github.com/ClangBuiltLinux/cbl-meetup-2023/blob/9b399fe8f3b886d549105a82068e3a441e496b46/nathan_making_llvm_faster_with_build_time_optimization_technologies.pdf

TL;DR: PGO and BOLT can give huge wins, LTO not so much.

It was pretty wild to see how much PGO made a difference, almost twice as fast in some cases... The kernel.org LLVM toolchains I provide are built with PGO and BOLT for this reason:

https://mirrors.edge.kernel.org/pub/tools/llvm/

2
7
2
hyeyoo

Hyeonggon Yoo

Reply to @cwayne@hachyderm.io
@cwayne because of time or money?
1
0
1
hyeyoo

Hyeonggon Yoo

Reply to @ljs
@ljs @vbabka
That's not 'alone' at least... XD
FYI I'm gonna drink today again so the toot's updated
1
0
2
hyeyoo

Hyeonggon Yoo

Reply to @pascaldragon@metalhead.club
@pascaldragon

Oh, in logical mode destination APIC can be encoded as indicating a set of processors instead of a processor.

Thanks!!
1
0
1
hyeyoo

Hyeonggon Yoo

Reply to @vbabka
@vbabka Ofc I didn't drink all of them alone :)
1
0
1
hyeyoo

Hyeonggon Yoo

Edited 11 months ago
I WILL (NEVER) DRINK AGAIN
1
0
4
hyeyoo

Hyeonggon Yoo

Edited 11 months ago
Hmm, I'm having difficulty understanding how interrupts from PCIe devices (with MSI-X support) can be distributed to different processors.

Only an address (to an Local APIC) can be assigned to an interrupt vector?
1
0
0
hyeyoo

Hyeonggon Yoo

Reply to @monsieuricon
@monsieuricon can I subscribe to it right?
1
0
2
hyeyoo
repeated
monsieuricon

K. Ryabitsev

Yes, you heard it right, we're moving away from patches sent via email.

The fax number you should use from now on is 1-900-555-1212.
16
169
356
hyeyoo
repeated
vbabka

Vlastimil Babka

I reduce maintainer burnout by deleting as much of the subsystem as possible.
2
13
31
hyeyoo
repeated
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

Reply to @ljs

@ljs

ohh, that explains @vbabka toot, I had been wondering already. 😄

Side note:

/me wonders if he should add some pseudo madeup wisdom like "some people want to become maintainers; wise people try to avoid it." here. 🙃

1
1
3
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: