Profiling memory usage

[David Zeuthen]

On Thu, 2006-11-30 at 21:53 +0000, Richard Hughes wrote:
> Yes, this is most sane. I'm in the middle of exams right now, so hacking
> will have to wait until Sunday.

Busy times it seems! For me too, sorry for being slow.

> I've attached the differences from HAL coldplugging, and getting udev to
> do it for us using udevsend. In particular, there are a few devices
> missing, and a few with different names. Kay, is there any known reason
> for this? David assured me the code paths were 99% the same for hal and
> udev, but I'm wondering if this 1% causes the differences. :-)

Perhaps. It definitely seems like we are missing a few devices. Kay
claims it should make no difference. Something to look into... Kay?

> I'm running udev-095-14 (FC6) but can try CVS/git if you think this
> might be worth trying.
> 
> For now, ignore the bus traffic generated using udevsend, I think we can
> just suppress it from the HAL side. With regard to waiting for coldplug
> to finish, I guess we can just poll /sys/kernel/uevent_seqnum, but is
> there a nicer way?

Kay?

> What about the battery class patch (send a couple of weeks ago) - I know
> you want Danny to give it the once over,but do you like the general idea
> of using glib set property and the general style?

Looked generally good to me. Danny?

    David