All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Longland <redhatter@gentoo.org>
To: Vadivelan@soc-soft.com
Cc: linux-mips@linux-mips.org
Subject: Re: 64-bit Linux kernel
Date: Tue, 17 Jan 2006 14:28:24 +1000	[thread overview]
Message-ID: <43CC7268.9070001@gentoo.org> (raw)
In-Reply-To: <4BF47D56A0DD2346A1B8D622C5C5902C012B2A36@soc-mail.soc-soft.com>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

Vadivelan@soc-soft.com wrote:
> Hi,
> 	I would like to know the differences between the 32-bit and
> 64-bit Linux kernel. Also does the MIPS port of Linux have support for
> 64-bit. Kindly provide me your invaluable inputs.
> Thanking you in advance.

In short, yes, Linux does support 64-bit kernels on MIPS processors.

It entirely depends on the target machine.  Some *have* to run 64-bit
kernels (e.g. the Octane, Indigo2 Impact...etc.), others can run either
32-bit or 64-bit (e.g. O2, with sufficiently old kernel... Indy,
Cobalt...etc).  Others, are strictly 32-bit only. (anything with a
MIPS-1, MIPS-2 or MIPS32 CPU).

It is worth noting that not all applications lend themselves to running
a 64-bit kernel.  1 + 1 will take just as long to calculate in 32-bit as
it does in 64-bit. :-)

> The information contained in this e-mail message and in any annexure is
> confidential to the  recipient and may contain privileged information.

In which case, why on earth did you send this email to a public email
list? ;-)
-- 
Stuart Longland (aka Redhatter)              .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer  '.'` :
. . . . . . . . . . . . . . . . . . . . . .   .'.'
http://dev.gentoo.org/~redhatter             :.'

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

      reply	other threads:[~2006-01-17  4:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  4:02 64-bit Linux kernel Vadivelan
2006-01-17  4:02 ` Vadivelan
2006-01-17  4:28 ` Stuart Longland [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=43CC7268.9070001@gentoo.org \
    --to=redhatter@gentoo.org \
    --cc=Vadivelan@soc-soft.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.