public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: ltt-dev@lists.casi.polymtl.ca
Cc: linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: LTTng 0.165 for 2.6.31.5 : refactoring/cleanup
Date: Tue, 3 Nov 2009 01:17:53 -0500	[thread overview]
Message-ID: <20091103061753.GA5815@Krystal> (raw)

Hi,

I just finished testing the LTTng refactoring. It consists of:

- Change design to inheritance for channels and buffers.
  - Eliminate structure duplication for locking/allocation level of buffer and
    channel.
  - Remove now unnecessary krefs.
- Fix cpu hotplug for timers.
- Cleanups.

Impact:
- Cleaner code.
- Simpler structures for channel/buffers.
- Smaller d-cache footprint.

It also permits to change the license of all LTTng modules needed both
for kernel and user-space tracing to dual LGPL/GPL license.

Due to the size of this change, review and testing would be very
welcome. I decided to do it in a separate patch on top of the tree
rather than rebasing. Considering the size of this modification, going
over the modified code on a file by file basis rather than looking at
the patch itself is probably easier.

I decided to mark the "locked" and "irqoff" locking schemes as "BROKEN"
for now and focus on the lockless scheme. We could re-create them if
needed by deriving from the lockless code-base.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

             reply	other threads:[~2009-11-03  6:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  6:17 Mathieu Desnoyers [this message]
2009-11-09 15:27 ` LTTng 0.166 for 2.6.31.5 : refactoring/cleanup - 32-bit fix Mathieu Desnoyers

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=20091103061753.GA5815@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=rostedt@goodmis.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