<feed xmlns='http://www.w3.org/2005/Atom'>
<title>phosphor-objmgr/MAINTAINERS, branch master</title>
<subtitle>OpenBMC Phosphor object manager sources</subtitle>
<id>https://git.raptorcs.com/git/phosphor-objmgr/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/phosphor-objmgr/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-objmgr/'/>
<updated>2018-11-15T15:39:58+00:00</updated>
<entry>
<title>maintainers: Update committers</title>
<updated>2018-11-15T15:39:58+00:00</updated>
<author>
<name>Brad Bishop</name>
<email>bradleyb@fuzziesquirrel.com</email>
</author>
<published>2018-11-15T15:39:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-objmgr/commit/?id=af1aa756a11fff49bc459a826741232f061a0d63'/>
<id>urn:sha1:af1aa756a11fff49bc459a826741232f061a0d63</id>
<content type='text'>
Ed wrote the c++ mapper.  Matt has been hacking on the mapper a lot
lately as well.  It makes sense that they have committer access.

Change-Id: I48cb7e2c32324f395136c4adbdfbcdcc41da894a
Signed-off-by: Brad Bishop &lt;bradleyb@fuzziesquirrel.com&gt;
</content>
</entry>
<entry>
<title>Implement Mapper in C++/sdbusplus/asio</title>
<updated>2018-09-28T13:24:45+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2018-06-12T00:46:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-objmgr/commit/?id=605206314f23710ef8a429745f139c891630588f'/>
<id>urn:sha1:605206314f23710ef8a429745f139c891630588f</id>
<content type='text'>
This commit attempts to reimplement the mapper using C++/sdbusplus
in the hopes of improving performance both at startup (lower priority)
and runtime (higher priority).

After this patch, performance seems to be greatly improved.  On an unloaded system, full
introspection of all daemons clocks in at 2.23 seconds for the worst
case.  Prelimiary tests show this to be 7X faster than the existing
client.  Expect this to come down slightly once associations are
implemented, as that will introduce some overhead.

It should not yet be considered complete although it does function.
The things that still need doing are:

1. Implement the configurable whitelist/blacklist that the existing
manage implements.  Today they are compiled in.

Tested By:
time busctl call xyz.openbmc_project.ObjectMapper
/xyz/openbmc_project/object_mapper xyz.openbmc_project.ObjectMapper
GetSubTree sias "/" 0 1 xyz.openbmc_project.State.Chassis
a{sa{sas}} 1 "/xyz/openbmc_project/state/chassis0" 1
"xyz.openbmc_project.State.Chassis" 2
"org.freedesktop.DBus.ObjectManager" "xyz.openbmc_project.State.Chassis"

C++ implementation
real 0m0.092s
user 0m0.040s
sys  0m0.010s

Python implementation
real 0m0.416s
user 0m0.010s
sys  0m0.030s

Also has been tested using reboots, daemon dropouts and reconnects.

Change-Id: I46ca8c273df09261cb2a2448a3570a601ea8e9f4
Signed-off-by: Ed Tanous &lt;ed.tanous@intel.com&gt;
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
Signed-off-by: Matt Spinler &lt;spinler@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Add MAINTAINERS file</title>
<updated>2018-06-05T02:39:43+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2018-05-18T16:54:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-objmgr/commit/?id=3b30b9add424e884a2cbc965726ffc9a901cc08c'/>
<id>urn:sha1:3b30b9add424e884a2cbc965726ffc9a901cc08c</id>
<content type='text'>
Change-Id: I17831666541617209514efaa8b1fa512aa9831ca
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
</content>
</entry>
</feed>
