From: Kumar Gala <galak@kernel.crashing.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
Li Yang <leoli@freescale.com>, Paul <paulus@samba.org>,
Vitaly Bordug <vbordug@ru.mvista.com>
Subject: Re: [PATCH] rheap: eliminates internal fragments caused by alignment
Date: Tue, 19 Jun 2007 18:04:32 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706191804100.27810@gate.crashing.org> (raw)
In-Reply-To: <1182269845.2969.117.camel@gentoo-jocke.transmode.se>
On Tue, 19 Jun 2007, Joakim Tjernlund wrote:
> On Mon, 2007-06-18 at 13:48 +0200, Joakim Tjernlund wrote:
> > On Mon, 2007-06-18 at 19:29 +0800, Li Yang wrote:
> > > The patch adds fragments caused by rh_alloc_align() back to free list, instead
> > > of allocating the whole chunk of memory. This will greatly improve memory
> > > utilization managed by rheap.
> > >
> > > It solves MURAM not enough problem with 3 UCCs enabled on MPC8323.
> > >
> > > Signed-off-by: Li Yang <leoli@freescale.com>
> > > ---
> >
> > For what it is worth:
> > I have tested this patch and it solves the problem with 3 UCCs
> > as ethernet for me. This fixes a regression introduced after 2.6.20
> > Please consider for 2.6.22
> > Acked-by: Joakim Tjernlund <joakim.tjernlund@transmode.se>
>
> I noticed Paulus pull request to Linus and this patch wasn't
> included. I really want to see it included.
>
I'll push (or request pull) from Linus tonight for this to go into 2.6.22
- k
next prev parent reply other threads:[~2007-06-19 23:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 11:29 [PATCH] rheap: eliminates internal fragments caused by alignment Li Yang
2007-06-18 11:48 ` Joakim Tjernlund
2007-06-19 16:17 ` Joakim Tjernlund
2007-06-19 23:04 ` Kumar Gala [this message]
2007-06-18 12:14 ` Pantelis Antoniou
2007-06-18 12:25 ` Joakim Tjernlund
2007-06-18 12:31 ` Pantelis Antoniou
2007-06-18 13:24 ` Joakim Tjernlund
2007-06-19 4:02 ` Li Yang-r58472
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=Pine.LNX.4.64.0706191804100.27810@gate.crashing.org \
--to=galak@kernel.crashing.org \
--cc=joakim.tjernlund@transmode.se \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=vbordug@ru.mvista.com \
/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).