From: Anthony PERARD <anthony.perard@citrix.com>
To: Xen Devel <xen-devel@lists.xen.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH V2 0/2] Cleanup: flexarray taking gc.
Date: Thu, 4 Oct 2012 17:18:40 +0100 [thread overview]
Message-ID: <1349367522-16695-1-git-send-email-anthony.perard@citrix.com> (raw)
This two patches do a bit of cleanup in the memomy managment in libxl,
regarding the use of flexarray.
The first one modify flexarray_make to take gc as argument and update every
user in libxl to pass gc and to not call flexarray_free anymore.
The second one does some cleanup only in libxl_json to make it use the gc.
Change since v1:
- Change order of the two patch to not end up with leaks.
- Add a comment on the first patch to tell why it OK to store the gc in the
flexarray struct.
- Keep the _free functions (libxl__json_object_free and flexarray_free, as
they can be used if gc in NOGC.
Anthony PERARD (2):
libxl: Have flexarray using the GC
libxl_json: Use libxl alloc function.
tools/libxl/flexarray.c | 48 ++++++++++++++---------
tools/libxl/flexarray.h | 7 +++-
tools/libxl/libxl.c | 99 ++++++++++--------------------------------------
tools/libxl/libxl_dm.c | 15 ++------
tools/libxl/libxl_json.c | 93 ++++++++++-----------------------------------
tools/libxl/libxl_pci.c | 18 ++-------
tools/libxl/libxl_qmp.c | 29 ++------------
7 files changed, 83 insertions(+), 226 deletions(-)
--
Anthony PERARD
next reply other threads:[~2012-10-04 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 16:18 Anthony PERARD [this message]
2012-10-04 16:18 ` [PATCH V2 1/2] libxl: Have flexarray using the GC Anthony PERARD
2012-10-04 17:31 ` Ian Jackson
2012-10-04 19:59 ` Anthony PERARD
2012-10-04 16:18 ` [PATCH V2 2/2] libxl_json: Use libxl alloc function Anthony PERARD
2012-10-04 17:32 ` Ian Jackson
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=1349367522-16695-1-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xen.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 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).