Posts
168
Following
31
Followers
77
Maintaining DAMON (https://damonitor.github.io). All opinions are my own.
sj
repeated
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

The next instalment of Linus vs. Kent – and Linus seems to be on the edge:

"[…] I'm contemplating just removing entirely from the [ ] mainline tree. Because you show again and again that you have no interest in trying to make mainline work. […]"

For the full discussion, start here: https://lore.kernel.org/all/cphtxla2se4gavql3re5xju7mqxld4rp6q4wbqephb6by5ibfa@5myddcaxerpb/t/#m631c24cd07f5820a4cbff8f25dff1d1a0c3cf2e7 (the quote is from one of the later mails from Linus).

6
5
5
sj
repeated
gustavoars@fosstodon.org

Gustavo A. R. Silva tux

Reply to @gustavoars@fosstodon.org

"[...] Always remember: upstream Linux kernel development is highly social. 😉"

1
2
2
sj
repeated
vbabka

Vlastimil Babka

Wonder how many more "strikes" are needed? I think we've seen far too many already. Heck, even the Phoronix commenters seem to think enough is enough.

RE: https://masto.ai/@phoronix/113257686368572007
1
2
5
sj

sj

Just posted[1] 2024-Q3 DAMON news letter. It contains a number of news regarding new features, more users, repos reorganizations, and conference talks.

[1] https://lore.kernel.org/20241001191425.588219-1-sj@kernel.org

#linux #kernel #damon
0
1
2
sj

sj

Monthly downloads of DAMON user-space tool (DAMO)[1] from PyPI took about 18 months to surpass 2,000. About only 7 months after that, it exceeded 4,000 today!

[1] https://github.com/damonitor/damo

#linux #kernel #damon #damo
0
1
2
sj
repeated
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

, which allows scheduling policies to be implemented as programs, has been merged for 6.12:

https://git.kernel.org/torvalds/c/88264981f2082248e892a706b2c5004650faac54

See https://lwn.net/Articles/922405/ for a description of what it does and https://lwn.net/Articles/972710/ for the controversy it caused that is the reason why it took so long to land in mainline.

0
5
3
sj
repeated
phoronix@masto.ai

Phoronix

Sched_ext Merged For Linux 6.12 - Scheduling Policies As BPF Programs

Linux 6.12 is shaping up to be a heck of a kernel update! Following real-time "PREEMPT_RT" going mainline after twenty years and many other kernel features merged this week, Linus Torvalds just pulled in the much anticipated sched_ext code!..
https://www.phoronix.com/news/Linux-6.12-Lands-sched-ext

0
2
1
sj

sj

Edited 1 month ago
My Kernel Memory Management LPC Micro Conference talk titled "DAMON: Long-term Plans for Kernel That {Just Works,Extensible}" was successful.
The video[1] and slides[2] are available. I was obviously nervous since I forgot contents of the slides due to the great talks from two previous speakers (I highly recommend you to watch those). I like it though, since it reminds me how humble I am ;)

[1] https://www.youtube.com/live/CTWQ-d7pj5s?feature=shared&t=20182
[2] https://lpc.events/event/18/contributions/1768/

#linux #kernel #damon #linuxplumbers
0
5
3
sj

sj

MM pull request for Linux v6.12-rc1 is posted[1] by Andrew Morton. Important fixes / cleanups for DAMON are included:

- mm/damon/lru_sort: adjust local variable to dynamic allocation
- misc fixups for DAMON {self,kunit} tests
- replace per-quota region priorities histogram buffer with per-context one
- Docs/damon: update GitHub repo URLs and maintainer-profile

I believe it is a good list of changes for next LTS kernel candidate.

[1] https://lore.kernel.org/20240920023317.f20c9ecbb2a2f4bf382d831c@linux-foundation.org

#linux #kernel #mm #damon
0
1
1
sj
repeated
monsieuricon

K. Ryabitsev

Lots of people thanked me for my work on b4 this week. It feels very nice, but I want to remind everyone that b4 wouldn't be possible without public-inbox. Please email Eric Wong (privately) and thank him for his work -- I am pretty sure he can use some good vibes.
0
6
19
sj

sj

Found an interesting academic paper preprint that optimizing THP using DAMON and BPF: "eBPF-mm: Userspace-guided memory management in
Linux with eBPF" (https://arxiv.org/pdf/2409.11220)

#linux #kernel #damon #bpf #thp
0
1
1
sj

sj

Edited 2 months ago
CONFIG_DAMON is enabled on Debian kernel! https://salsa.debian.org/kernel-team/linux/-/merge_requests/1172

#linux #kernel #damon
0
2
6
sj
repeated
uis@pone.social

uis

Reply to @gregkh

@gregkh
> but it's not obvious how and no one has come up with a way to do so. Maybe now they will have some more incentive :)

Not sure if this is what you want, but there is __attribute__((tainted_args)) since gcc 12.

1
1
2
sj
repeated
gregkh

Greg K-H

This "untrusted data" patch series from Benno Lossin is the result of conversations at last weekend's Rust Linux kernel conference in Copenhagen:

https://lore.kernel.org/all/20240913112643.542914-1-benno.lossin@proton.me/

It's not a "silver bullet" for why we should be using rust in the Linux kernel, but it is a "big giant sledgehammer" to help squash and prevent from happening MANY common types of kernel vulnerabilities and bugs (remember, "all input is evil!" and this change forces you to always be aware of that, which is something that C in the kernel does not.)

I had always felt that Rust was the future for what we need to do in Linux, but now I'm sure, because if we can do stuff like this, with no overhead involved (it's all checked at build time), then we would be foolish not to give it a real try.

And yes, I've asked for this for years from the C developers, and maybe we can also do it there, but it's not obvious how and no one has come up with a way to do so. Maybe now they will have some more incentive :)
5
123
166
sj

sj

Reply to @sj
Now I'm onboarding onto the next ship. So from now on, the views expressed herein do not reflect the views of their employers ;)
1
0
4
sj
repeated
corbet

Jonathan Corbet

I have often complained that, even though thousands of developers are paid to work on the Linux kernel, there is not a single person whose job it is to write documentation for the kernel. The problem is wider than that, though: Alejandro Colomar, who has been maintaining the man pages collection for the last four years, can no longer afford to do it for free.

https://lwn.net/ml/all/4d7tq6a7febsoru3wjium4ekttuw2ouocv6jstdkthnacmzr6x@f2zfbe5hs7h5
5
84
66
sj

sj

Reply to @authentic_sammj@ozlabs.house
Edited 2 months ago
@authentic_sammj Thank you, Sam! It's not easy for me to say whether it will be cool. You know me ;) But I will hopefully share the next news soon. Let's see.
1
0
1
sj

sj

Edited 2 months ago
Today was my last day at Amazon. So from now on, the views expressed herein are those of the speakers;
They _do_ reflect the views of their employers (myself), until another announcement ;)
3
0
5
sj

sj

A new squad member has arrived from Germany.
0
1
2
sj

sj

Very impressive CXL-based memory tiering performance of HMSDK is shared[1] with a cool video. It is the grateful result of a collaboration between DAMON community and SK hynix. It was never a one-side help, but a collaboration. DAMON also gained its ability to do tiered memory managements from the collaboration.

I'm grateful to be a part of the work. I was always impressed and learned many things from SK hynix' innovative ideas and constructive discussions. I'm looking forward to continued collaborations and next outputs!

[1] https://www.linkedin.com/posts/honggyukim_ai-hpc-cxl-activity-7236734372266000385-zYuk?utm_source=share&utm_medium=member_desktop

#linux #kernel #damon
0
1
1
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: