linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-mm@kvack.org, Russell King <linux@arm.linux.org.uk>
Subject: Re: [RFC] memblock; Properly handle overlaps
Date: Sun, 06 Mar 2011 08:50:19 +1100	[thread overview]
Message-ID: <1299361819.8833.954.camel@pasglop> (raw)
In-Reply-To: <1299361063.8833.953.camel@pasglop>


> Can you reply inline next to the respective code ? It would make things
> easier :-)
> 
> > 1. after check with bottom, we need to update the size. otherwise when we
> > checking with top, we could use wrong size, and increase to extra big.
> 
> You mean adding this ?
> 
> 			/* We continue processing from the end of the
> 			 * coalesced block.
> 			 */
> 			base = rgn->base + rgn->size;
> + 			size = end - base;
> 
> I suppose you are right. Interestingly enough I haven't trigged that in
> my tests, I'll add an specific scenario to trigger that problem.
> 
> > 2. before we calling memblock_remove_region() in the loop, it could render
> > blank array. So need to move the special case handle down.
> 
> I'm not sure I understand what you mean here.
> 
> The blank array always has a count of 1, so memblock_remove_region()
> should be safe to call at any time. I can see how __memblock_remove()
> can hit the case of a blank array but that seems harmless to me.

Ok, I see there is indeed a problem as we do an i-- in this case and so
end up in an infinite loop trying to remove the fake entry. I'll fix
that too. Thanks.

Cheers,
Ben.

> Thanks.
> 
> Ben.
> 
> > Thanks
> > 
> > Yinghai
> > 
> > ---
> >  mm/memblock.c |   32 +++++++++++++++++++-------------
> >  1 file changed, 19 insertions(+), 13 deletions(-)
> > 
> > Index: linux-2.6/mm/memblock.c
> > ===================================================================
> > --- linux-2.6.orig/mm/memblock.c
> > +++ linux-2.6/mm/memblock.c
> > @@ -279,15 +279,6 @@ static long __init_memblock memblock_add
> >  	phys_addr_t end = base + size;
> >  	long i;
> >  
> > -	/* If the array is empty, special case, replace the fake
> > -	 * filler region and return
> > -	 */
> > -	if ((type->cnt == 1) && (type->regions[0].size == 0)) {
> > -		type->regions[0].base = base;
> > -		type->regions[0].size = size;
> > -		return 0;
> > -	}
> > -
> >  	/* First try and coalesce this MEMBLOCK with others */
> >  	for (i = 0; i < type->cnt; i++) {
> >  		struct memblock_region *rgn = &type->regions[i];
> > @@ -330,11 +321,17 @@ static long __init_memblock memblock_add
> >  			 * coalesced block.
> >  			 */
> >  			base = rgn->base + rgn->size;
> > -		}
> >  
> > -		/* Check if e have nothing else to allocate (fully coalesced) */
> > -		if (base >= end)
> > -			return 0;
> > +			/*
> > +			 * Check if We have nothing else to allocate
> > +			 * (fully coalesced)
> > +			 */
> > +			if (base >= end)
> > +				return 0;
> > +
> > +			/* Update left over size */
> > +			size = end - base;
> > +		}
> >  
> >  		/* Now check if we overlap or are adjacent with the
> >  		 * top of a block
> > @@ -360,6 +357,15 @@ static long __init_memblock memblock_add
> >  		}
> >  	}
> >  
> > +	/* If the array is empty, special case, replace the fake
> > +	 * filler region and return
> > +	 */
> > +	if ((type->cnt == 1) && (type->regions[0].size == 0)) {
> > +		type->regions[0].base = base;
> > +		type->regions[0].size = size;
> > +		return 0;
> > +	}
> > +
> >   new_block:
> >  	/* If we are out of space, we fail. It's too late to resize the array
> >  	 * but then this shouldn't have happened in the first place.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 


--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-03-05 21:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05  4:05 [RFC] memblock; Properly handle overlaps Benjamin Herrenschmidt
2011-03-05  5:46 ` Yinghai Lu
2011-03-05  7:56   ` Benjamin Herrenschmidt
2011-03-05 19:14     ` Yinghai Lu
2011-03-05 21:37       ` Benjamin Herrenschmidt
2011-03-05 21:50         ` Benjamin Herrenschmidt [this message]
2011-03-05 22:08           ` Benjamin Herrenschmidt
2011-03-05 22:01         ` Yinghai Lu
2011-03-05 22:19           ` Benjamin Herrenschmidt
2011-03-05 23:20             ` Yinghai Lu
2011-03-06  0:49               ` Benjamin Herrenschmidt
2011-03-06  1:20                 ` Yinghai Lu

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=1299361819.8833.954.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).