From: Christoph Hellwig <hch@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: hch@infradead.org, nhorman@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: add tracepoints to socket api
Date: Tue, 27 Jan 2009 12:23:23 -0500 [thread overview]
Message-ID: <20090127172323.GA7635@infradead.org> (raw)
In-Reply-To: <20090127.092017.40699485.davem@davemloft.net>
On Tue, Jan 27, 2009 at 09:20:17AM -0800, David Miller wrote:
> From: Christoph Hellwig <hch@infradead.org>
> Date: Tue, 27 Jan 2009 12:18:57 -0500
>
> > Do we now have lttng in linux-next? Otherwise these trace point would
> > be useless there without more patching.
>
> We're merging this stuff to solve the chicken and egg
> problem wherein the lttng tree merge is basically
> stalled.
>
> If the individual subsystem annotations go in, the hope
> is that they'll have less to merge and thus it's more likely
> to actually happen.
I'm rather concerned as I haven't seen any progress on the lttng core
lately. I'd really prefer to have a version in close to mergeable shape
first, that's actively beeing pushed. Adding the instrumentation is
trivial as seen by this small patch, but getting the core right (and who
knows if that involves changing the way actual instrumentation works, it's
not like that hasn't changed n million times yet) is essential.
next prev parent reply other threads:[~2009-01-27 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 19:59 [PATCH] net: add tracepoints to socket api Neil Horman
2009-01-27 1:22 ` David Miller
2009-01-27 1:31 ` Arnaldo Carvalho de Melo
2009-01-27 5:57 ` David Miller
2009-01-27 12:09 ` Neil Horman
2009-01-27 14:07 ` Neil Horman
2009-01-27 17:18 ` Christoph Hellwig
2009-01-27 17:20 ` David Miller
2009-01-27 17:23 ` Christoph Hellwig [this message]
2009-01-27 18:21 ` David Miller
2009-01-27 18:47 ` Christoph Hellwig
2009-01-27 20:42 ` Neil Horman
2009-01-28 21:28 ` Neil Horman
2009-02-01 10:02 ` David Miller
2009-02-01 18:53 ` Neil Horman
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=20090127172323.GA7635@infradead.org \
--to=hch@infradead.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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 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.