linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>, hollisb@us.ibm.com
Subject: Re: common flatdevtree code
Date: Wed, 6 Sep 2006 13:52:07 +1000	[thread overview]
Message-ID: <17662.17895.852128.729679@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20060831184020.GA13494@mag.az.mvista.com>

Mark A. Greer writes:

> I'm doing some fairly massive rework to my patches so it'll take
> another day or two (plus 4 day weekend for me).  In the meantime,
> this is what I've done to your code.  :)

Any further progress on this?  I need an ft library for the prep
bootwrapper changes I'm planning.

I don't like the approach of doing a malloc for the whole blob every
time you make a property larger though.  I'm going to be adding quite
a few nodes and properties, potentially, and with a simple-minded
malloc (such as you get in a bootwrapper) it's likely to chew through
a lot of memory unnecessarily.  I would rather be able to start with
an existing blob and pull it apart once, add stuff to it, then put it
back together, doing a small number of mallocs in the process.

> I still plan on changing it a bit to use ft_next in a few more routines
> (e.g., ft_dump_blob).  ft_next has a clumsy interface but I like the fact

The interface might look nicer if we had a structure for the tag,
name, value and length.  Then there would only be one parameter
instead of the four you have at the moment.

Paul.

  reply	other threads:[~2006-09-06  3:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 18:40 common flatdevtree code Mark A. Greer
2006-09-06  3:52 ` Paul Mackerras [this message]
2006-09-06 18:14   ` Mark A. Greer
2006-09-07  0:36   ` Mark A. Greer
2006-09-07  7:43     ` Hollis Blanchard
2006-09-07 18:27       ` Mark A. Greer
2006-09-07 22:23         ` Hollis Blanchard
2006-09-08  0:56           ` Mark A. Greer
2006-09-08  1:11             ` Mark A. Greer
2006-09-08 13:23             ` Paul Mackerras
2006-09-08 16:51               ` Mark A. Greer
2006-09-19 19:45               ` Mark A. Greer
2006-09-27 22:32                 ` Paul Mackerras
2006-09-27 22:55                   ` Hollis Blanchard
2006-09-27 23:41                   ` Segher Boessenkool
2006-09-27 23:52                     ` Hollis Blanchard
2006-09-28  0:51                       ` Segher Boessenkool
2006-09-28 19:34                       ` Mark A. Greer

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=17662.17895.852128.729679@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=hollisb@us.ibm.com \
    --cc=mgreer@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).