mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dong Feng" <middle.fengdong@gmail.com>
To: "Christoph Lameter" <clameter@sgi.com>
Cc: "Jan Engelhardt" <jengelh@linux01.gwdg.de>,
	"Andi Kleen" <ak@suse.de>,
	"Nick Piggin" <nickpiggin@yahoo.com.au>,
	"Arjan van de Ven" <arjan@infradead.org>,
	"Paul Mackerras" <paulus@samba.org>,
	"David Howells" <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: The 3G (or nG) Kernel Memory Space Offset
Date: Wed, 30 Aug 2006 00:16:27 +0800	[thread overview]
Message-ID: <a2ebde260608290916o696bf5d6odbca254af079f2a8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608290908500.18149@schroedinger.engr.sgi.com>

No, please do not get me wrong. Or perhaps please tolerate my poor English.

My intention is just trying to understand whether there is an absolute
rationality for a design choice or it just has to have a choice and
the choice can be made arbitrarily.

Sorry again if my English cause any misunderstanding.


2006/8/30, Christoph Lameter <clameter@sgi.com>:
> On Wed, 30 Aug 2006, Dong Feng wrote:
>
> > Or perhaps this offset is just some personal favor. Say if the first
> > kernel designer decided to locate kernel at 2-3G linear address, then
> > 2G offset would have appeared in code. Is this the case?
>
> Well this is the second time that you suggest that the reason for
> technical decisions have to do with personal favors. Are you trying to
> provoke us into answering your question?
>
>

  reply	other threads:[~2006-08-29 16:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 14:15 Dong Feng
2006-08-29 14:32 ` Andi Kleen
2006-08-29 14:36 ` Jan Engelhardt
2006-08-29 16:01   ` Dong Feng
2006-08-29 16:05     ` Arjan van de Ven
2006-08-29 16:30       ` Jan Engelhardt
2006-08-29 16:44         ` Jeremy Fitzhardinge
2006-08-29 16:12     ` Christoph Lameter
2006-08-29 16:16       ` Dong Feng [this message]
2006-08-29 16:42     ` Jeremy Fitzhardinge
2006-08-29 18:37       ` Peter Grandi
2006-08-29 21:15         ` Jeremy Fitzhardinge
2006-08-30  6:11           ` Jan Engelhardt
2006-08-30  4:32 linux

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=a2ebde260608290916o696bf5d6odbca254af079f2a8@mail.gmail.com \
    --to=middle.fengdong@gmail.com \
    --cc=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=clameter@sgi.com \
    --cc=dhowells@redhat.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome