All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Lance Yang <lance.yang@linux.dev>
Cc: SJ Park <sj@kernel.org>,
	mst@redhat.com, david@kernel.org, damon@lists.linux.dev,
	linux-mm@kvack.org, virtualization@lists.linux.dev,
	ryncsn@gmail.com, kunwu.chan@gmail.com, lianux.mm@gmail.com,
	baohua@kernel.org, xueyuan.chen21@gmail.com
Subject: Re: [FYI] DAMON and virtio-balloon in DeepSeek's DSec paper
Date: Fri, 25 Sep 2026 03:13:31 -0700	[thread overview]
Message-ID: <20260925101332.49502-1-sj@kernel.org> (raw)
In-Reply-To: <20260925054408.10431-1-lance.yang@linux.dev>

Hi Lance,

On Fri, 25 Sep 2026 13:44:08 +0800 Lance Yang <lance.yang@linux.dev> wrote:

> Hi all,
> 
> I was reading DeepSeek's new DSec paper[1] and found a nice use of DAMON
> and virtio-balloon:
> 
> With this kind of workload, an agent may read a file once and never touch
> it again, while those pages remain in the guest page cache. Without memory
> pressure in the guest, they can stay cached even though the host would
> like that memory back ...
> 
> The trick is DAMON + virtio-balloon free-page reporting :) DAMON reclaims
> cold file pages from the guest page cache; buddy gets a chance to coalesce
> them into reportable blocks, and virtio-balloon passes those blocks to
> Firecracker. Firecracker can then drop the host backing with MADV_DONTNEED.
> 
> And it worked: time-integrated host memory use fell by 21.2%, while peak
> usage stayed about the same, with no significant CPU overhead. Pretty cool
> to see these pieces show up in another real, large-scale system :)

Thank you for sharing this, Lance!

> 
> Kernel work still changes the world. Cheers to that!

Indeed, the community is making the work a great place.

> 
> Anyhow, I still don't know DAMON and virtio-balloon as well as I should
> (mostly I just know the people who built them) :P

Please feel free to ask any question to DAMON community and me, whenever you
get :)

> 
> [1] https://arxiv.org/html/2609.22978

I only briefly read the paper.  But it looks like DeepSeek's DAMON usage is
similar to AWS' DAMON usage [1] for their serverless service.

While I was in AWS, I proposed [2] a more advanced version called
Access/Contiguity-aware Memory Autoscaling (ACMA).  After the RFC idea v2 [2],
no progress is made so far, though.  I shortly covered it in LSFMMBPF'25 [3],
but all I mentioned was that the project is suspended.  Recently a useer has
personally reached out to me asking the status of ACMA.  It is too early stage
of the discussion to say or promise something in my humble perspective, though.

[1] https://cdn.amazon.science/ee/a4/41ff11374f2f865e5e24de11bd17/resource-management-in-aurora-serverless.pdf
[2] https://lore.kernel.org/all/20240512193657.79298-1-sj@kernel.org/
[3] https://lore.kernel.org/all/20250121183103.42877-1-sj@kernel.org/


Thanks,
SJ

[...]


  parent reply	other threads:[~2026-09-25 10:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  5:44 [FYI] DAMON and virtio-balloon in DeepSeek's DSec paper Lance Yang
2026-09-25  5:57 ` Lian Wang
2026-09-25  6:46   ` KunWu Chan
2026-09-25  7:04 ` David Hildenbrand (Arm)
2026-09-25  7:28   ` Lian Wang
2026-09-25  8:15   ` Lance Yang
2026-09-25 10:03     ` David Hildenbrand (Arm)
2026-09-25 10:16     ` Gao Xiang
2026-09-25 10:27       ` Gao Xiang
2026-09-25 10:13 ` SJ Park [this message]
2026-09-29 12:32 ` Jialiang Huang
2026-09-29 12:41   ` Gao Xiang
2026-09-29 12:50     ` Jialiang Huang
2026-09-30  3:36     ` Muchun Song
2026-09-30  7:24       ` Gao Xiang
2026-09-30  9:37         ` Muchun Song
2026-09-30 10:33           ` Gao Xiang
2026-09-29 16:56   ` SJ Park
2026-09-30  3:07     ` Lian Wang
2026-09-30  8:08       ` SJ Park
2026-09-29 18:14   ` Pratyush Mallick

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=20260925101332.49502-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=baohua@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=kunwu.chan@gmail.com \
    --cc=lance.yang@linux.dev \
    --cc=lianux.mm@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=mst@redhat.com \
    --cc=ryncsn@gmail.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xueyuan.chen21@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 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.