From: Willy Tarreau <w@1wt.eu>
To: Dan Malek <ppc6dev@digitaldans.com>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 0/3] 8xx: Large page(8MB) support for 2.4
Date: Mon, 10 Oct 2011 18:29:09 +0200 [thread overview]
Message-ID: <20111010162909.GB21699@1wt.eu> (raw)
In-Reply-To: <39B024CE-70A2-4D32-A29C-5702C7D2D6CF@digitaldans.com>
Hi an,
On Mon, Oct 10, 2011 at 09:22:09AM -0700, Dan Malek wrote:
>
> Hi Joakim.
>
> On Oct 10, 2011, at 4:38 AM, Joakim Tjernlund wrote:
>
> >This adds Large page support for 8xx and uses it
> >for all kernel RAM....
>
> >- Dan, what do you think :)
>
> Since you asked, yes it looks great :-) Now, can we
> get this into a more contemporary kernel? I'm
> actually working on an 8xx project that may have
> a few years of life left.
At the pace of current 2.4, I'm sure the code won't have change
much a few years from now :-) It would be nice to know by now if
the current longterm branches work OK or not though.
Cheers,
Willy
next prev parent reply other threads:[~2011-10-10 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 11:38 [PATCH 0/3] 8xx: Large page(8MB) support for 2.4 Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 1/3] 8xx: replace _PAGE_EXEC with _PAGE_PSE Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 2/3] 8xx: Support LARGE pages in TLB code Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 3/3] 8xx: Use LARGE pages for kernel RAM Joakim Tjernlund
2011-10-10 16:22 ` [PATCH 0/3] 8xx: Large page(8MB) support for 2.4 Dan Malek
2011-10-10 16:29 ` Willy Tarreau [this message]
2011-10-10 16:45 ` Joakim Tjernlund
2011-10-10 18:03 ` Dan Malek
2011-10-11 7:42 ` Joakim Tjernlund
[not found] ` <OF5A487DD5.BE515A85-ONC1257926.0029F008-C1257926.002A6323@LocalDomain>
2011-10-12 21:36 ` Joakim Tjernlund
2011-10-13 1:08 ` Dan Malek
2011-10-13 14:00 ` Joakim Tjernlund
2011-10-13 15:48 ` Dan Malek
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=20111010162909.GB21699@1wt.eu \
--to=w@1wt.eu \
--cc=linuxppc-dev@ozlabs.org \
--cc=ppc6dev@digitaldans.com \
--cc=scottwood@freescale.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