All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH 1/5] dbus: Coalesce InterfacesAdded/Removed signals
Date: Fri, 26 Feb 2016 14:27:28 -0600	[thread overview]
Message-ID: <56D0B530.1060306@gmail.com> (raw)
In-Reply-To: <1455765612-6577-1-git-send-email-andrew.zaborowski@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Hi Andrew,

On 02/17/2016 09:20 PM, Andrew Zaborowski wrote:
> When multiple interfaces are added or removed during the same main loop
> cycle emit one signal per object with all the interfaces added or
> removed.  Move the signals to the idle callback.
> ---
>   ell/dbus-service.c | 337 ++++++++++++++++++++++++++++++++++++++++-------------
>   1 file changed, 257 insertions(+), 80 deletions(-)

I looked over these and was fine with them.  I went ahead and applied 
all five patches.  I did tweak some naming afterward to be more 
consistent.  Please eyeball that and let me know if you're okay with those.

One question I have is whether we could save a bit of space by 
coalescing the path and object pointers in the three record objects into 
a single structure.  E.g. go from

struct interface_add_record {
         char *path;
         struct object_node *object;
         struct l_queue *instances;
};

struct interface_remove_record {
         char *path;
         struct object_node *object;
         struct l_queue *interface_names;
};

struct property_change_record {
         char *path;
         struct object_node *object;
         struct interface_instance *instance;
         struct l_queue *properties;
};

to:

struct emit_signal_record {
	char *path;
	struct object_node *object;
	struct l_queue *removed_interface_names;
	struct l_queue *added_interface_instances;
	struct l_queue *changed_properties;
};

?

Regards,
-Denis

      parent reply	other threads:[~2016-02-26 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18  3:20 [PATCH 1/5] dbus: Coalesce InterfacesAdded/Removed signals Andrew Zaborowski
2016-02-18  3:20 ` [PATCH 2/5] dbus: Coalesce PropertiesChanged signals Andrew Zaborowski
2016-02-26 20:30   ` Denis Kenzior
2016-02-29  9:21     ` Andrzej Zaborowski
2016-02-29 15:43       ` Denis Kenzior
2016-02-29 21:26       ` Denis Kenzior
2016-02-18  3:20 ` [PATCH 3/5] dbus: Move standard interface name defines to public header Andrew Zaborowski
2016-02-18  3:20 ` [PATCH 4/5] examples: dbus-service: Use interface name macros Andrew Zaborowski
2016-02-18  3:20 ` [PATCH 5/5] unit: Update PropertyChanged value check Andrew Zaborowski
2016-02-26 20:27 ` Denis Kenzior [this message]

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=56D0B530.1060306@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ell@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.