All of lore.kernel.org
 help / color / mirror / Atom feed
From: Venkatraman S <venkat@linaro.org>
To: kzak@redhat.com
Cc: util-linux@vger.kernel.org, arnd.bergmann@linaro.org,
	Venkatraman S <venkat@linaro.org>
Subject: Re: [RFC PATCH 0/4] Adding useful information into swap partition header
Date: Mon, 22 Oct 2012 22:34:06 +0530	[thread overview]
Message-ID: <CAFSEfh03NHoWjWh2A0wx_eu8xZFvzU6jvRpLtmF-uYxNUwTE3A@mail.gmail.com> (raw)
In-Reply-To: <1350925048-31084-1-git-send-email-venkat@linaro.org>

On 22 October 2012 22:27, Venkatraman S <venkat@linaro.org> wrote:
> Trying some of the ideas bounced around in lkml for
> optimizing swap on flash (eMMC / SD) media [1], we can start
> to add useful information into swapheader without breaking
> compatibility.
> Such information can help the kernel swap management algo
> to tune itself to the geometry of flash devices (erase block
> size and page size etc).
> Some more features (like command line override) are still
> under development. In long term, libblkid/mkswap can be extended
> to even detect this information by timing attacks,
> even if sysfs parameters are not present.
>
Oops: Some reference links were missed in the cover letter..

[1] https://lkml.org/lkml/2012/3/30/410

  parent reply	other threads:[~2012-10-22 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 16:57 [RFC PATCH 0/4] Adding useful information into swap partition header Venkatraman S
2012-10-22 16:57 ` [RFC PATCH 1/4] libblkid/topology: add preferred_erase_size to topology probe Venkatraman S
2012-10-22 16:57 ` [RFC PATCH 2/4] mkswap: refactor header preparation Venkatraman S
2012-10-22 16:57 ` [RFC PATCH 3/4] mkswap: Add additional fields in swapheader Venkatraman S
2012-10-22 16:57 ` [PATCH 4/4] mkswap: Probe and embed useful block device info into swapheader Venkatraman S
2012-10-22 17:04 ` Venkatraman S [this message]
2012-10-23 12:16 ` [RFC PATCH 0/4] Adding useful information into swap partition header Karel Zak
2012-10-23 13:37   ` Venkatraman S
2012-11-08  9:44     ` Karel Zak

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=CAFSEfh03NHoWjWh2A0wx_eu8xZFvzU6jvRpLtmF-uYxNUwTE3A@mail.gmail.com \
    --to=venkat@linaro.org \
    --cc=arnd.bergmann@linaro.org \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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 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.