public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Jones <davej@redhat.com>, Pavel Machek <pavel@ucw.cz>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm 5/6] mm: Print first block offset for swap areas
Date: Tue, 26 Sep 2006 22:13:25 +0200	[thread overview]
Message-ID: <200609262213.26274.rjw@sisk.pl> (raw)
In-Reply-To: <20060926123907.4801a022.akpm@osdl.org>

On Tuesday, 26 September 2006 21:39, Andrew Morton wrote:
> On Sat, 23 Sep 2006 12:10:54 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > In order to use a swap file with swsusp we need to know the offset at which
> > its swap header is located.  However, the swap header is always located in the
> > first page block of the swap file and it's quite easy to make sys_swapon() print
> > the offset of the swap file's (or swap partition's) first page block.
> 
> Why is this needed?  The swapfile's pathname is present in /proc/swaps, so
> an application can read that, do the FIBMAP and rewrite grub.conf without
> needing to parse dmesg?

Well, this is not needed, but it's useful if you have no such application and
want to set up things manually. ;-)

  reply	other threads:[~2006-09-26 20:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23  9:57 [PATCH -mm] swsusp: Add support for swap files Rafael J. Wysocki
2006-09-23 10:01 ` [PATCH -mm 1/6] swsusp: Use partition device and offset to identify swap areas Rafael J. Wysocki
2006-09-23 10:02 ` [PATCH -mm 2/6] swsusp: Rearrange swap-handling code Rafael J. Wysocki
2006-09-23 10:04 ` [PATCH -mm 3/6] swsusp: Use block device offsets to identify swap locations Rafael J. Wysocki
2006-09-26 19:38   ` Andrew Morton
2006-09-26 20:04     ` Rafael J. Wysocki
2006-09-26 21:51       ` Rafael J. Wysocki
2006-09-23 10:08 ` [PATCH -mm 4/6] swsusp: Add resume_offset command line parameter Rafael J. Wysocki
2006-09-26 19:38   ` Andrew Morton
2006-09-26 20:10     ` Rafael J. Wysocki
2006-09-23 10:10 ` [PATCH -mm 5/6] mm: Print first block offset for swap areas Rafael J. Wysocki
2006-09-26 19:39   ` Andrew Morton
2006-09-26 20:13     ` Rafael J. Wysocki [this message]
2006-09-26 20:49       ` Andrew Morton
2006-09-26 21:04         ` Rafael J. Wysocki
2006-09-23 10:13 ` [PATCH -mm 6/6] swsusp: Document support for swap files Rafael J. Wysocki
2006-09-26 21:56   ` Rafael J. Wysocki
2006-09-23 10:17 ` [PATCH -mm] swsusp: Add " Pavel Machek
2006-09-23 20:30   ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2006-09-20 19:20 [PATCH -mm 0/6] " Rafael J. Wysocki
2006-09-20 19:54 ` [PATCH -mm 5/6] mm: Print first block offset for swap areas Rafael J. Wysocki
2006-09-21 21:32   ` Pavel Machek
2006-09-21 22:10     ` Dave Jones
2006-09-21 22:46       ` Rafael J. Wysocki
2006-09-21 23:58         ` Jason Lunz
2006-09-22 10:57           ` Rafael J. Wysocki
2006-09-22 14:13             ` Jason Lunz
2006-09-22 14:18               ` Pavel Machek
2006-09-22 14:35                 ` Jason Lunz
2006-09-22 14:37                   ` Pavel Machek
2006-09-22 14:32               ` Rafael J. Wysocki
2006-09-22 14:33                 ` Pavel Machek

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=200609262213.26274.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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