public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	Theodore Tso <tytso@MIT.EDU>,
	        systemtap@sources.redhat.com
Subject: Re: Discussion at Linux Foundation Japan Symposium
Date: Wed, 24 Dec 2008 08:48:00 -0000	[thread overview]
Message-ID: <20081224033922.A7942FC3B7@magilla.sf.frob.com> (raw)
In-Reply-To: Masami Hiramatsu's message of  Tuesday, 23 December 2008 18:26:32 -0500 <495173A8.7060405@redhat.com>

> As far as I read the wiki, it seems that you'll make a tool to compress
> debuginfo. Out of curiosity, how small would you expect that the tool
> can reduce debuginfo? 

I wouldn't like to speculate.  I plan to just get on with it and progress
quickly to tools sufficient to make concrete measurements.

> (Can we select(edit) how much info the dwarf
> includes by that tool, or just use compressed format?)

I have not made particular plans for anything that would lose information.
But the intent is to take an approach that will make it fairly easy to
write and experiment with new DWARF-transforming tools in the future.

> By the way, if the development will take more than two years, it might be
> belated, at last.

I don't think I understood this sentence.  I certainly would be much
happier if we'd embarked on this work two years ago, but we didn't,
and we have yet to really begin.  The idea that it could take
anything like two years of actual development on this to produce
results seems just ludicrous to me, if that's what you meant.
Unless the effort goes horribly awry, I'll know a great deal more
concrete about it in a month, and the hope going in is to have quite
a lot of it done in two months.

> Unfortunately, we are in a severe situation. I don't mean
> that you give up the effort. Instead of that, I recommend you to run the
> project with target users (for example, kernel developers and systemtap
> developers), do rapid prototyping and embrace their feedbacks. It could
> take more time, but you can continue to attract users and give us hope!

I don't know what it means to "run the project with target users".
The actual tool development is something for DWARF and toolchain
experts to do, and I don't expect kernel developers to devote their
time to that just because they would benefit from the deployment of
such tools (as will many other kinds of developers--this is not
solely for the benefit of systemtap).  Of course the project is open
to everyone who wants to contribute, and of course development of
new tools will be driven by the concerns of their potential users.


Thanks,
Roland

  reply	other threads:[~2008-12-24  3:40 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22 18:22 Frank Ch. Eigler
2008-12-22 20:38 ` Theodore Tso
2008-12-22 22:41   ` Frank Ch. Eigler
2008-12-23  0:33     ` Theodore Tso
2008-12-23  0:34       ` Masami Hiramatsu
2008-12-23  0:44         ` Theodore Tso
2008-12-23 21:13           ` Roland McGrath
2008-12-23 22:13           ` Masami Hiramatsu
2008-12-23 14:28       ` Frank Ch. Eigler
2008-12-23 22:21     ` Roland McGrath
2008-12-23 22:33       ` Masami Hiramatsu
2008-12-23 22:44         ` Roland McGrath
2008-12-24  3:40           ` Masami Hiramatsu
2008-12-24  8:48             ` Roland McGrath [this message]
2008-12-24 18:14               ` Masami Hiramatsu
2008-12-24 19:26                 ` Roland McGrath
2008-12-24 21:02                 ` Theodore Tso
2008-12-26 18:17                   ` Roland McGrath
2008-12-23 23:27       ` Theodore Tso
2008-12-24  6:11         ` Masami Hiramatsu
2009-01-10  2:48           ` Theodore Tso
2009-01-11 16:29             ` Frank Ch. Eigler
2009-01-12 18:18               ` Masami Hiramatsu
2009-01-12 18:53                 ` Frank Ch. Eigler
2009-01-12 19:29                   ` Masami Hiramatsu
2009-01-12 19:26               ` Theodore Tso
2009-01-12 20:01                 ` Frank Ch. Eigler
2009-01-12 19:05             ` Jason Baron
2009-01-12 19:52               ` Theodore Tso
2009-01-12 20:32                 ` Frank Ch. Eigler
2009-01-08  9:22         ` Roland McGrath
2009-01-10  1:33           ` Theodore Tso
2008-12-22 23:34   ` Masami Hiramatsu
  -- strict thread matches above, loose matches on Subject: below --
2008-12-18  8:33 Satoshi OSHIMA
2008-12-18  8:59 ` KOSAKI Motohiro
2008-12-18  9:07 ` Jun Koi
2008-12-18  9:21   ` jidong xiao
2008-12-18  9:28     ` Jun Koi
2008-12-18  9:35   ` KOSAKI Motohiro
2008-12-18  9:37     ` Jun Koi
2008-12-18  9:42       ` Jun Koi
2008-12-18  9:46         ` KOSAKI Motohiro
2008-12-18  9:58     ` K.Prasad
2008-12-18 10:02       ` KOSAKI Motohiro
2008-12-18 10:21         ` K.Prasad
2008-12-18 15:52         ` Masami Hiramatsu
2008-12-18 15:41 ` Masami Hiramatsu
2008-12-18 17:11 ` Frank Ch. Eigler
2008-12-19  0:08   ` KOSAKI Motohiro
2008-12-19  0:58     ` Frank Ch. Eigler
2008-12-19  1:39       ` KOSAKI Motohiro
2008-12-19 23:51       ` William Cohen
2008-12-20  1:51         ` Richard J Moore
2008-12-20 14:27         ` Masami Hiramatsu
2008-12-19  0:45   ` Masami Hiramatsu

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=20081224033922.A7942FC3B7@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=fche@redhat.com \
    --cc=mhiramat@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=tytso@MIT.EDU \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).