Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rishabh@soc-soft.com
Cc: linux-mips@linux-mips.org
Subject: Re: Memory Management HAndling
Date: Fri, 11 Mar 2005 13:36:31 +0000	[thread overview]
Message-ID: <1110548190.15943.46.camel@localhost.localdomain> (raw)
In-Reply-To: <4BF47D56A0DD2346A1B8D622C5C5902C61E22B@soc-mail.soc-soft.com>

On Gwe, 2005-03-11 at 05:25, Rishabh@soc-soft.com wrote:
> These macros can handle memory pages in KSEG0. Any suggestions on how
> can they be changed for addressing memory present in HIGHMEM. Since VA
> will not be in linear relation with mem_map.

Take a look at how kmap() works on x86 and how the mappings are used.

  parent reply	other threads:[~2005-03-11 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  5:25 Memory Management HAndling Rishabh
2005-03-11  5:25 ` Rishabh
2005-03-11 13:36 ` Alan Cox [this message]
2005-03-11 15:59   ` Ralf Baechle
2005-03-11 17:06     ` Manish Lachwani
2005-03-11 17:22       ` Ralf Baechle
2005-03-11 15:58 ` Ralf Baechle

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=1110548190.15943.46.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Rishabh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox