[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020909210508i7e8b1b3bif61dcb5b576c878d@mail.gmail.com>
Date: Mon, 21 Sep 2009 15:08:04 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: Hugh Dickins <hugh.dickins@...cali.co.uk>
Cc: ngupta@...are.org, Greg KH <greg@...ah.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ed Tomlinson <edt@....ca>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
linux-mm-cc <linux-mm-cc@...top.org>,
kamezawa.hiroyu@...fujitsu.com, nishimura@....nes.nec.co.jp
Subject: Re: [PATCH 2/4] send callback when swap slot is freed
Hi Hugh,
On Mon, Sep 21, 2009 at 2:55 PM, Hugh Dickins
<hugh.dickins@...cali.co.uk> wrote:
> Though exporting the swap_info_struct still bothers me, and it
> seems convoluted that the block device should have a method, so
> swapon can call the block device, so the block device can call
> swapfile.c to install a callout, so that swapfile.c can call the
> block device when freeing swap. I'm not saying there is a better
> way, just that I'd be glad of a better way.
I guess we can combine my ->swapon() hook in struct
block_device_operations with Nitin's set_swap_free_notify() function
to avoid exporting struct swap_info_struct. Alternatively, we could
add the ->swap_free() hook too struct block_device_operations. In any
case, I don't think we can do the setup at sys_open() if we keep
Nitin's hook as struct swap_info_struct is not set up until
sys_swapon().
Pekka
--
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