From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: [patch] Stat vs slurp vs linux 2.6.22
Date: Wed, 25 Jul 2007 14:59:00 -0000 [thread overview]
Message-ID: <1185375592.3597.40.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46A75077.2020706@redhat.com>
Hi Andrew,
On Wed, 2007-07-25 at 09:30 -0400, Andrew Cagney wrote:
> > It might make sense to rewrite slurp as a normal java class so these
> > cross C/Java error handling issues. Is there a reason for slurp to have
> > to be written in C/CNI?
> >
> -> memory pressure; notice how it does a callback
> -> performance
Interesting. It does feel a little like a premature optimization though,
seeing that we are finding bugs in it because of the Java/C/CNI mixture
of error and memory handling that are hard to track down.
How precisely do callbacks work in slurp (I have to admit that I
haven't noticed them) and why can't you do that with a normal java
implementation?
Thanks,
Mark
next prev parent reply other threads:[~2007-07-25 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 11:30 Mark Wielaard
2007-07-25 13:30 ` Andrew Cagney
2007-07-25 14:59 ` Mark Wielaard [this message]
2007-07-25 15:39 ` Andrew Cagney
2007-07-26 7:24 ` Mark Wielaard
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=1185375592.3597.40.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).