public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org
Cc: Changli Gao <xiaosuo@gmail.com>, Jens Axboe <jens.axboe@oracle.com>
Subject: [RELEASE] LTTng 0.199 for Linux 2.6.33
Date: Mon, 15 Mar 2010 13:03:11 -0400	[thread overview]
Message-ID: <20100315170311.GA390@Krystal> (raw)

Hi everyone,

I just released an updated LTTng tree/tarball that is now based on the 2.6.33
kernel. As always, comments and testing results are welcome.

Website:
http://lttng.org

Kernel tree:
http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git
git://git.kernel.org/pub/scm/linux/kernel/git/compudj/linux-2.6-lttng.git

Tarballs:
http://lttng.org/files/lttng/patch-2.6.33-lttng-0.199.tar.bz2

There has been some changes in the way splice() works between 2.6.32 and 2.6.33
(commit cc56f7de7f00d188c7c4da1e9861581853b9e92f). It now checks for NULL llseek
fop in addition to check for the no_llseek. In LTTng, we use the offset value
directly in our own implementation of the splice_read fop, so there is no point
in having a llseek fop.  The solution I used to bypass this check is to create
my own copy of "no_llseek" in ltt-relay-splice.c, which does basically nothing,
but makes do_splice() happy.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
Operating System Efficiency Consultant
EfficiOS Inc.
http://www.efficios.com

                 reply	other threads:[~2010-03-15 17:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100315170311.GA390@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=xiaosuo@gmail.com \
    /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