public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Alessandro Suardi <alessandro.suardi@oracle.com>
Cc: Andrew Morton <akpm@digeo.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, pbadari@us.ibm.com
Subject: Re: Oracle 9.2 OOMs again at startup in 2.5.4[78]
Date: Tue, 19 Nov 2002 11:38:07 -0800	[thread overview]
Message-ID: <20021119193807.GN23425@holomorphy.com> (raw)
In-Reply-To: <3DDA8C18.1000903@oracle.com>

On Tue, Nov 19, 2002 at 08:08:08PM +0100, Alessandro Suardi wrote:
> The patch you actually include seems to be a combination of
>     ChangeSet 1.373.204.73 2002/05/28 22:01:57 torvalds@home.transmeta.com
>       Remove re-use of "struct mm_struct" at execve() time.
>       This will eventually allow us to copy argc/argv without
>       any intermediate storage (removing current argument size
>       limitations).
> and
>     ChangeSet 1.373.221.1 2002/05/28 22:55:46 torvalds@home.transmeta.com
>       Allocate new mm_struct for execve() early, so that we have
>       access to it by the time we start copying arguments.

This created some unusual startup problems for DB2 also, but they went
away (for DB2) before anyone had figured out why they caused a startup
failure. ISTR badari dealing with this more directly (hence the cc:).

badari, do you remember more of what happened?


Thanks,
Bill

  parent reply	other threads:[~2002-11-19 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 14:22 Oracle 9.2 OOMs again at startup in 2.5.4[78] Alessandro Suardi
2002-11-19 14:34 ` Billy O'Connor
2002-11-19 18:54 ` Andrew Morton
2002-11-19 19:08   ` Alessandro Suardi
2002-11-19 19:26     ` Linus Torvalds
2002-11-19 19:38     ` William Lee Irwin III [this message]
2002-11-19 19:42       ` 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=20021119193807.GN23425@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@digeo.com \
    --cc=alessandro.suardi@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=torvalds@transmeta.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