From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: David Daney <ddaney.cavm@gmail.com>,
"aleksey.makarov@auriga.com" <aleksey.makarov@auriga.com>,
James Hogan <James.Hogan@imgtec.com>,
Paul Burton <Paul.Burton@imgtec.com>,
"david.daney@cavium.com" <david.daney@cavium.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ralf@linux-mips.org" <ralf@linux-mips.org>,
"davidlohr@hp.com" <davidlohr@hp.com>,
"kirill@shutemov.name" <kirill@shutemov.name>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@kernel.org" <mingo@kernel.org>
Subject: Re: [PATCH v2] MIPS64: Support of at least 48 bits of SEGBITS
Date: Sat, 16 May 2015 03:11:01 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.11.1505160305100.4923@eddie.linux-mips.org> (raw)
In-Reply-To: <55564319.7020502@imgtec.com>
On Fri, 15 May 2015, Leonid Yegoshin wrote:
> > Many processors support larger VA space than is utilized by the kernel.
> > A choice was made to reduce the size of the VA space in order to
> > reduce TLB handling overhead.
> >
> > If the true reason for the patch is to enable larger VA space, say that.
> > But is it really required by those processors you mention? I doubt it.
>
> Well, I was not aware about many processors capability, I can't find this kind
> of note anywhere.
The R10000 and friends all have a 44-bit virtual address space, so this
is no news to Linux. This is noted in <asm/processor.h> right above the
change you made there.
Maciej
next prev parent reply other threads:[~2015-05-16 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 1:34 Leonid Yegoshin
2015-05-15 10:39 ` Sergei Shtylyov
2015-05-15 16:28 ` David Daney
2015-05-15 19:03 ` Leonid Yegoshin
2015-05-16 2:11 ` Maciej W. Rozycki [this message]
2015-05-15 20:49 ` David Daney
2015-05-15 21:01 ` Leonid Yegoshin
2015-05-15 21:53 ` Ralf Baechle
2015-05-15 22:39 ` Leonid Yegoshin
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=alpine.LFD.2.11.1505160305100.4923@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=James.Hogan@imgtec.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=Paul.Burton@imgtec.com \
--cc=akpm@linux-foundation.org \
--cc=aleksey.makarov@auriga.com \
--cc=david.daney@cavium.com \
--cc=davidlohr@hp.com \
--cc=ddaney.cavm@gmail.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®