[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <d760cf2d1003050222m6e509ffaqa498645c52f7d98e@mail.gmail.com>
Date: Fri, 5 Mar 2010 15:52:13 +0530
From: Nitin Gupta <ngupta@...are.org>
To: Hugh Dickins <hugh.dickins@...cali.co.uk>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <greg@...ah.com>, Pekka Enberg <penberg@...il.com>,
andi@...stfloor.org, linux-kernel <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/3] ramzswap: Eliminate stale data in compressed memory
ramzswap driver creates RAM based block devices which can be
used (only) as swap disks. Pages swapped to these disks are
compressed and stored in memory itself.
However, these devices do not get any notification when a swap
slot is freed (swap_map[i] reaches 0). So, we cannot free memory
allocated corresponding to this swap slot. Such stale data can
quickly accumulate in (compressed) memory defeating the whole
purpose of such devices.
To overcome this problem, we now add a callback in 'struct swap_info_struct'
which is called as soon as a swap slot is freed.
Adding handler for this callback:
swapon notifier --> set_swap_free_notify(swap_type, fn)
Removing handler:
swapoff notifier --> set_swap_free_notify(swap_type, NULL)
Alternative approaches:
1) Add callback directly in 'struct block_device_operations' but
that is considered too hacky.
2) Use swap discard mechanism: It involves unncessary overhead of
allocating 'discard bio' requests and its too slow to serve ramzswap
needs.
drivers/staging/ramzswap/ramzswap_drv.c | 91 +++++++++++++++++++++++++++++
drivers/staging/ramzswap/ramzswap_drv.h | 1 +
drivers/staging/ramzswap/ramzswap_ioctl.h | 1 +
include/linux/swap.h | 16 +++++-
mm/swapfile.c | 78 ++++++++++++++++++++++++
5 files changed, 185 insertions(+), 2 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists