From: Christoph Rohland <cr@sap.com>
To: andersen@codepoet.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] sysinfo compatibility
Date: 22 Aug 2001 18:04:37 +0200 [thread overview]
Message-ID: <m3hev0w06i.fsf@linux.local> (raw)
In-Reply-To: <Pine.LNX.4.21.0108211137340.1320-100000@localhost.localdomain> <m34rr12ueb.fsf@linux.local> <20010821114640.A25151@codepoet.org> <m3bsl81tm0.fsf@linux.local> <20010822094554.A9760@codepoet.org>
In-Reply-To: <20010822094554.A9760@codepoet.org>
Hi Erik,
On Wed, 22 Aug 2001, Erik Andersen wrote:
> On Wed Aug 22, 2001 at 08:44:39AM +0200, Christoph Rohland wrote:
>>
>> BTW I appreciate the basics of the change for 2.4, but I don't
>> agree that we should break cases which worked before. (And the
>> comment in the sources is plain wrong that 2.2 failed in these
>> cases)
>
> But 2.2 _did_ fail. If you take a linux 2.2.x system, add 4 Gigs of
> swap, and then use sysinfo(), the sizes you get back are junk...
But if you add 3.9GB it is ok. Also with 3.9GB RAM. And that's a quite
common machine in our environment.
If one of these overflows I agree that the 2.4 scheme is better. But
we should keep compatibility as long as we have no single field which
overflows.
And that's what my patch implements.
Greetings
Christoph
next prev parent reply other threads:[~2001-08-22 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 8:03 [Patch] sysinfo compatibility Christoph Rohland
2001-08-21 10:59 ` Hugh Dickins
2001-08-21 13:50 ` Alan Cox
2001-08-21 17:30 ` Christoph Rohland
2001-08-21 18:40 ` Alan Cox
2001-08-22 6:40 ` Christoph Rohland
2001-08-21 17:30 ` Christoph Rohland
2001-08-21 17:46 ` Erik Andersen
2001-08-22 6:44 ` Christoph Rohland
2001-08-22 15:45 ` Erik Andersen
2001-08-22 16:04 ` Christoph Rohland [this message]
2001-08-21 18:40 ` Hugh Dickins
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=m3hev0w06i.fsf@linux.local \
--to=cr@sap.com \
--cc=andersen@codepoet.org \
--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