From: Milton Miller <miltonm@bga.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org, Tim Abbott <tabbott@ksplice.com>
Subject: Re: [PATCH 1/2] vmlinux.lds.h: allow people to set a smaller rootfs alignment
Date: Fri, 11 Jun 2010 02:30:50 -0500 [thread overview]
Message-ID: <1276241450_14430@mail4.comsite.net> (raw)
In-Reply-To: <4C11CEAA.5020703@zytor.com>
On Thu, 10 Jun 2010 at around 22:50:34 -0700, H. Peter Anvin wrote:
> On 06/09/2010 12:42 AM, Mike Frysinger wrote:
> >
> > i have no problem changing the default to 4 since it works fine on
> > Blackfin systems. your analysis of the source alignment also seems
> > reasonable ... i assume that the 8 byte fields in the source cpio
> > arent referenced directly, otherwise it'd cause problems on 64bit
> > systems that require 64bit values to be naturally aligned.
> >
> > beyond that, i dont see why any larger alignment values would be
> > required since this source archive isnt executed directly. it gets
> > expanded into a ramfs and then freed with the rest of the init stuff.
> >
>
> We have talked for a long time about incrementally freeing the initramfs
> as it is decoded, which might help systems which are using most of their
> memory for an initramfs image...
at which time the author of said theoritcal patch that might possibly
need page alignment would only need to update vmlinux.lds.h and not all
the architectures vmlinux.lds.S files.
milton
prev parent reply other threads:[~2010-06-11 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 18:14 [PATCH 1/2] vmlinux.lds.h: allow people to set a smaller rootfs alignment Mike Frysinger
2010-06-05 18:14 ` [PATCH 2/2] Blackfin: use " Mike Frysinger
2010-06-07 23:27 ` [PATCH 1/2] vmlinux.lds.h: allow people to set a " Tim Abbott
2010-06-09 7:20 ` Milton Miller
2010-06-09 7:42 ` Mike Frysinger
2010-06-09 7:51 ` Geert Uytterhoeven
2010-06-11 5:50 ` H. Peter Anvin
2010-06-11 7:30 ` Milton Miller [this message]
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=1276241450_14430@mail4.comsite.net \
--to=miltonm@bga.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tabbott@ksplice.com \
--cc=vapier.adi@gmail.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