mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick.Holloway@pyrites.org.uk (Nick Holloway)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.5.17
Date: 23 May 2002 13:17:34 +0100	[thread overview]
Message-ID: <acimku$qh2$1@alfie.demon.co.uk> (raw)
In-Reply-To: <86256BC1.0076F247.00@smtpnotes.altec.com>

In <86256BC1.0076F247.00@smtpnotes.altec.com> Wayne.Brown@altec.com writes:
> In comparing /proc/meminfo in 2.4.19-pre8 and 2.5.17 I see that there is very
> little difference except that the information gtop relies upon is missing.  The
> lines it needs aren't changed or rearranged, just gone altogether.  Was there
> any particular purpose for that, other than breaking programs like gtop?

I confess to submitting the patch to Linus to remove the compatability
lines when 2.5.0 was created.

The change that made the first two lines redundant was originally made in
1.3.68[1], and the intention was that they would removed -- the comment
in get_meminfo had:

    Tagged format, for easy grepping and expansion. The above will go away
    eventually, once the tools have been updated.

As I had an application that parsed /proc/meminfo around the time of
the change, I wrote the parser to handle the new format in preparation
for the old format going away.  Others would have done the same.

Someone mentioned that this compatability was still present during
2.4 development, so I made a mental note to submit a patch when 2.5
development started.

> I'm a firm believer that adding something new to a system should
> never break existing functionality unless absolutely necessary.  Was it
> necessary in this case, or was it done because someone was offended that
> it wasn't "clean" enough?

Where possible, interfaces should not be changed for the sake of change,
but you shouldn't keep old interfaces because that way lies bloat.

One of the beauties of Linux (IMO) is that broken interfaces don't have
to be maintained ad-infinitum.  It should be expected that interfaces
may be broken during the development series of kernels, and the tools
have a chance to catch up during this cycle.

The interface that gtop (implicitly) required is that "Swap:" should be
the 3rd line in /proc/meminfo.  You'll never get anyone to admit that
this is the interface to /proc/meminfo that should be maintained.

-
[1] http://groups.google.com/groups?selm=4glagm%24pno%40treflan.shout.net

-- 
 `O O'  | Nick.Holloway@pyrites.org.uk
// ^ \\ | http://www.pyrites.org.uk/

  reply	other threads:[~2002-05-23 12:17 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22 20:00 Linux-2.5.17 Wayne.Brown
2002-05-23 12:17 ` Nick Holloway [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-22  3:02 Linux-2.5.17 Wayne.Brown
2002-05-22  7:12 ` Linux-2.5.17 Zwane Mwaikambo
2002-05-22 11:49 ` Linux-2.5.17 Nick Holloway
2002-05-21 23:20 Linux-2.5.17 Wayne.Brown
2002-05-21 23:29 ` Linux-2.5.17 Russell King
2002-05-21 23:33 ` Linux-2.5.17 Joel Jaeggli
2002-05-21 18:52 Linux-2.5.17 Wayne.Brown
2002-05-21 21:30 ` Linux-2.5.17 David S. Miller
2002-05-22  7:36   ` Linux-2.5.17 Helge Hafting
2002-05-21  5:16 Linux-2.5.17 Linus Torvalds
2002-05-21 13:58 ` Linux-2.5.17 Roman Zippel
2002-05-21 16:06   ` Linux-2.5.17 Linus Torvalds
2002-05-21 18:36     ` Linux-2.5.17 Roman Zippel
2002-05-21 18:53       ` Linux-2.5.17 Linus Torvalds
2002-05-21 23:35         ` Linux-2.5.17 Roman Zippel
2002-05-22  0:10           ` Linux-2.5.17 Linus Torvalds
2002-05-22  0:31             ` Linux-2.5.17 Roman Zippel
2002-05-22  0:54               ` Linux-2.5.17 Linus Torvalds
2002-05-22  2:17                 ` Linux-2.5.17 David S. Miller
2002-05-22  2:40                   ` Linux-2.5.17 Linus Torvalds
2002-05-22  2:57                     ` Linux-2.5.17 David S. Miller
2002-05-22  3:21                       ` Linux-2.5.17 Linus Torvalds
2002-05-22  8:06                         ` Linux-2.5.17 David Lang
2002-05-22 14:14                         ` Linux-2.5.17 Dave McCracken
2002-05-22 16:10                           ` Linux-2.5.17 Linus Torvalds
2002-05-22 13:45                 ` Linux-2.5.17 Roman Zippel
2002-05-22 16:08                   ` Linux-2.5.17 Linus Torvalds
2002-05-22 10:54 ` Linux-2.5.17 Martin Dalecki
2002-05-22 12:04   ` Linux-2.5.17 Alexander Viro
2002-05-22 13:07     ` Linux-2.5.17 Martin Dalecki
2002-05-22 14:38       ` Linux-2.5.17 Alexander Viro
2002-05-22 13:42         ` Linux-2.5.17 Martin Dalecki
2002-05-22 16:55       ` Linux-2.5.17 Jan Kara
2002-05-22 12:14   ` Linux-2.5.17 Russell King
2002-05-22 12:36     ` Linux-2.5.17 Martin Dalecki
2002-05-22 16:02     ` Linux-2.5.17 Linus Torvalds
2002-05-22 15:04       ` Linux-2.5.17 Martin Dalecki
2002-05-22 16:58         ` Linux-2.5.17 Jan Kara
2002-05-22 16:08           ` Linux-2.5.17 Martin Dalecki
2002-05-22 17:56             ` Linux-2.5.17 Jan Kara
2002-05-22 16:56               ` Linux-2.5.17 Martin Dalecki
2002-05-22 18:17                 ` Linux-2.5.17 Jan Kara
2002-05-22 18:36                   ` Linux-2.5.17 Russell King
2002-05-22 13:06   ` Linux-2.5.17 Alan Cox
2002-05-22 11:19 ` Linux-2.5.17 Russell King
2002-05-22 11:27   ` Linux-2.5.17 David S. Miller
2002-05-22 16:23   ` Linux-2.5.17 Linus Torvalds
2002-05-24 13:59 ` Linux-2.5.17 Martin Dalecki

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='acimku$qh2$1@alfie.demon.co.uk' \
    --to=nick.holloway@pyrites.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®