All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: clean up mem_map usage ... part 1
Date: Fri, 16 Aug 2002 14:58:10 -0700	[thread overview]
Message-ID: <3D5D7572.DD7ACA23@zip.com.au> (raw)
In-Reply-To: 2448940000.1029533820@flay

"Martin J. Bligh" wrote:
> 
> > Looks good, thanks.  I'll nail an unneeded typecast in there.
> >
> > My queue runneth over at present, and the kmap patches need to
> 
> I'm not suprised ;-) I can queue more stuff here rather than send it
> to your queue, but I'd like you to keep an eye on me before I go too far
> astray from what you want to see ;-)

Oh whatever.  If it's in my pile then a few more people get to
bang on it for a while.  Looks like a long backlog will become
a permanent state, so I'll need to do something more organised
there.

> > I won't send the rmap locking hacklets until we've nailed that
> > BUG in __free_pages_ok.
> 
> That seems to occur with 2.5.31, AFIACS, it's not the extra patches
> you have ... unless you mean just not stirring the pot at the moment.

Well yes.  The code at present is pretty much the same as well-tested 2.4
code which presumably will make it easier to find this bug.  Changing
the code now would increase the volume of suspect code.
 
> ...
> 2. mapnr. This is the index into the mem_map array. For contigmem,
> thats equiv to a pfn, and more or less made some sense.
> For discontigmem that's a nasty hack. We don't have a mem_map array,
> we have an lmem_map array per pg_data_t (aka node or memory chunk).
> But we somehow decided to define mem_map = PAGE_OFFSET, then
> retend the whole of the virtual address space is some kind of klunky
> mem_map array with holes in. So node_start_mapnr = lmem_map - mem_map ....
> except that's really arith on struct pages, so it's the distance / sizeof(struct page).
> So we have to align lmem_map allocations on a boundary of size sizeof(struct page),
> except that's really a boundary from PAGE_OFFSET, not absolute vaddr.
> Gack. Look at free_area_init_core. It's unpleasant ;-)

I wish you hadn't told me all that.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-08-16 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 20:45 clean up mem_map usage ... part 1 Martin J. Bligh
2002-08-16 21:22 ` Andrew Morton
2002-08-16 21:37   ` Martin J. Bligh
2002-08-16 21:58     ` Andrew Morton [this message]
2002-08-16 22:15       ` Martin J. Bligh
2002-08-17  0:32       ` Rik van Riel
2002-08-17  1:23         ` Andrew Morton

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=3D5D7572.DD7ACA23@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=linux-mm@kvack.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.