From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>, Cyp <cyp561@gmail.com>,
Minchan Kim <minchan.kim@gmail.com>,
driverdev <devel@driverdev.osuosl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ramzswap: Remove backing swap support
Date: Thu, 13 May 2010 18:15:31 +0300 [thread overview]
Message-ID: <4BEC1793.1010109@cs.helsinki.fi> (raw)
In-Reply-To: <1273740861-1900-1-git-send-email-ngupta@vflare.org>
Nitin Gupta wrote:
> Currently, each ramzswap device can be assigned
> a separate 'backing swap' file/partition. The ramzswap
> driver forwards swap I/O requests to this backing swap
> whenever an incompressible page is found.
>
> This feature adds nearly 700 lines of code and it
> also duplicates much of the swapon() functionality
> (for example, finding swap extents and so on). Removing
> this code makes the driver much simpler and should
> help its transition from staging to stable drivers
> area (drivers/block/).
>
> Similar functionality may be implemented if we can
> implement migrating pages across swap devices but the
> details have not yet been worked out.
>
> Support for _partitions_ as backing swap could be
> retained as it requires a few lines of code only.
> This part can be re-introduced later if above swap
> migration method turns out to be infeasible.
>
> More cleanups and code comments will be added soon.
>
> Signed-off-by: Nitin Gupta <ngupta@vflare.org>
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
next prev parent reply other threads:[~2010-05-13 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 8:54 Nitin Gupta
2010-05-13 15:15 ` Pekka Enberg [this message]
2010-05-16 4:20 ` Minchan Kim
2010-05-16 15:43 ` Nitin Gupta
2010-05-16 16:21 ` Greg KH
2010-05-16 16:50 ` Nitin Gupta
2010-05-16 23:58 ` Greg KH
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=4BEC1793.1010109@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=cyp561@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan.kim@gmail.com \
--cc=ngupta@vflare.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome