Re: dm: add swap_slot_free_notify handler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Understood. Now I’m developing some target which is using this interface locally, and I’ll send this patch again when I push this target to upstream.

From: Mike Snitzer <snitzer@xxxxxxxxxx>
Date: 2016년 9월 22일 목요일 오전 9:14
To: David <wonhong.kwon@xxxxxxx>
Cc: <agk@xxxxxxxxxx>, <dm-devel@xxxxxxxxxx>, '이건호' <gunho.lee@xxxxxxx>
Subject: Re: dm: add swap_slot_free_notify handler

On Wed, Sep 21 2016 at  7:09pm -0400,
Wonhong Kwon <wonhong.kwon@xxxxxxx> wrote:

swap_slot_free_notify callback has been added to block_device_operations to
allow freeing memory allocated by RAM-based swap device like zram or zswap
more aggressively.
In case of device mapper, it is also required if mapped target is being
used as swap device and it uses some in-memory metadata for swap entries.
This patch introduces swap_slot_free_notify callback into dm_blk_ops and
target device can implement its own handler to handle this via
slot_free_notify in target_type.
Signed-off-by: Wonhong Kwon <wonhong.kwon@xxxxxxx>

This change to DM core only makes sense once we have an upstream DM
target that implements slot_free_notify hook.

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux