mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Ric Wheeler <ricwheeler@gmail.com>,
	Christian Brandt <brandtc@psi5.com>,
	linux-kernel@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>
Subject: Re: swap storage alignment and stride size
Date: Thu, 16 Dec 2010 18:46:41 -0500	[thread overview]
Message-ID: <yq11v5h46xq.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <alpine.LSU.2.00.1012151627400.8734@tigran.mtv.corp.google.com> (Hugh Dickins's message of "Wed, 15 Dec 2010 16:42:33 -0800 (PST)")

>>>>> "Hugh" == Hugh Dickins <hughd@google.com> writes:

>> You called it a "header page". Does that imply that it is page sized?

Hugh> Yes.  (Rather a nuisance on a PowerPC system which sometimes uses
Hugh> a kernel with 4k pages and sometimes a kernel with 64k pages.)

Ok.


>> Or will it cause pages written to a 4k-aligned swap device to be
>> misaligned?

Hugh> No, the 4k-aligned remains 4k-aligned, of course.  But if you
Hugh> aligned your swap partition on, say, a 1MB boundary, and are
Hugh> thinking of working in aligned 1MB blocks, then it may be awkward
Hugh> that there's always this special 4k at the start (it could be
Hugh> written back each time even though it hasn't changed, but it's
Hugh> still an odd case).

Yeah, I got that. I just wanted to make sure that the header was not 32
bytes or something like that because that would be highly painful from
an I/O alignment perspective.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2010-12-16 23:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 17:03 Christian Brandt
2010-12-08 19:56 ` Ric Wheeler
2010-12-14 20:00   ` Martin K. Petersen
2010-12-15  4:57     ` Hugh Dickins
2010-12-15 19:30       ` Martin K. Petersen
2010-12-16  0:42         ` Hugh Dickins
2010-12-16 23:46           ` Martin K. Petersen [this message]
2010-12-17  0:15           ` Christian Brandt

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=yq11v5h46xq.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=brandtc@psi5.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ricwheeler@gmail.com \
    --cc=snitzer@redhat.com \
    /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