From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: William Lee Irwin III <wli@holomorphy.com>,
Andries Brouwer <Andries.Brouwer@cwi.nl>,
mita akinobu <amgta@yacht.ocn.ne.jp>,
linux-kernel@vger.kernel.org,
Alessandro Rubini <rubini@ipvvis.unipv.it>
Subject: Re: [util-linux] readprofile ignores the last element in /proc/profile
Date: Mon, 30 Aug 2004 01:25:43 +0200 [thread overview]
Message-ID: <20040829232543.GC24937@apps.cwi.nl> (raw)
In-Reply-To: <20040829212350.GX5492@holomorphy.com>
On Sun, Aug 29, 2004 at 02:23:50PM -0700, William Lee Irwin III wrote:
> The difference I cared the most about was algorithmic. A giant memcpy()
> of the profile buffer and making multiple passes over it is ridiculous.
> This was recoded as maintaining a buffer large enough to hold the
> length of the profile buffer spanning symbol currently being examined.
> In this way the memory resources required for it to operate are
> drastically reduced from multiple megabytes to just a few pages.
That is good - although so far I have not heard complaints
about readprofile's memory use. Maybe multiple MB is not
so excessive these days.
But improvement is always good.
On the other hand, I like stability. Maybe readprofile is just some
kind of throwaway utility, not very important, but nevertheless,
some people use it, and they have habits and hate to relearn,
and they have scripts, and hate to adapt these scripts.
So, if the internal code is improved, excellent, but I am not so
happy if the invocation is changed without a very good reason.
Maybe you can make a cross: your improved algorithm inside the
old framework with options and locale?
> The removal of -V was intentional, as I consider it bloat.
Don't you know that whenever there are complaints about software
the very first question is "which version?"?
> I wasn't really expecting much to come of it besides prodding people
> to clean up bloat. The reduced functionality alone likely precludes it
> from consideration for inclusion. Supposing that there is greater
> interest, which I don't expect, I can fix these things up and so on.
Well, you sent me something. I have three choices: take it as
replacement for the current version, ignore it, work on it.
I have no time to work on it, so am only happy with what you send
if it can replace the current version.
Andries
next prev parent reply other threads:[~2004-08-29 23:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 15:22 [util-linux] readprofile ignores the last element in /proc/profile mita akinobu
2004-08-29 16:22 ` William Lee Irwin III
2004-08-29 18:41 ` William Lee Irwin III
2004-08-29 19:26 ` Andries Brouwer
2004-08-29 21:23 ` William Lee Irwin III
2004-08-29 21:26 ` William Lee Irwin III
2004-08-29 23:25 ` Andries Brouwer [this message]
2004-08-30 0:26 ` William Lee Irwin III
2004-08-30 18:27 ` Paulo Marques
2004-08-30 20:48 ` William Lee Irwin III
2004-08-31 16:45 ` mita akinobu
2004-08-31 17:21 ` mita akinobu
2004-08-31 19:25 ` William Lee Irwin III
2004-08-31 19:45 ` William Lee Irwin III
2004-09-01 16:09 ` mita akinobu
2004-09-01 16:27 ` William Lee Irwin III
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=20040829232543.GC24937@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=amgta@yacht.ocn.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@ipvvis.unipv.it \
--cc=wli@holomorphy.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