mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: AHERRMAN@de.ibm.com, viro@ftp.linux.org.uk, heicars2@de.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH resubmit] do_mount: reduce stack consumption
Date: Fri, 4 Nov 2005 10:37:43 -0800	[thread overview]
Message-ID: <20051104103743.16f0ee06.akpm@osdl.org> (raw)
In-Reply-To: <20051104174506.GA4720@devserv.devel.redhat.com>

Arjan van de Ven <arjanv@redhat.com> wrote:
>
> On Fri, Nov 04, 2005 at 09:42:12AM -0800, Andrew Morton wrote:
>  > Andreas Herrmann <AHERRMAN@de.ibm.com> wrote:
>  > >
>  > > Obviously you missed the point that (depending on the compiler version,
>  > >  options etc.) do_move_mount() and do_add_mount() can be inlined.
>  > 
>  > I think we found a way of preventing the 3.x compiler from doing that.  Arjan,
>  > do you recall where we ended up with that problem?
> 
>  it was mostly caused by -funit-at-a-time that caused 3.x to go haywire. You
>  need to turn that off in general.

In that case, does s390 still have a problem that we need to be solving here?

(s390 doesn't implement CONFIG_DEBUG_STACK_USAGE.  Suggest you do so, then
stick a dump_stack() into do_exit()).

(dm is still doing very risky things though)

  reply	other threads:[~2005-11-04 18:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 15:53 Andreas Herrmann
2005-11-04 17:42 ` Andrew Morton
2005-11-04 17:45   ` Arjan van de Ven
2005-11-04 18:37     ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-04 10:50 Heiko Carstens
2005-11-04 11:48 ` Al Viro
2005-11-04 12:57   ` Heiko Carstens
2005-11-04 14:06     ` Al Viro
2005-11-04 22:03       ` Heiko Carstens
2005-11-04 16:48 ` Andrew Morton
2005-11-04 21:27   ` Heiko Carstens
2005-11-04 23:55     ` Adrian Bunk
2005-11-05  0:08       ` Andrew Morton
2005-11-05  1:15         ` cplk
2005-11-05  1:37           ` Andrew Morton
2005-11-05  5:37             ` Neil Brown

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=20051104103743.16f0ee06.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=AHERRMAN@de.ibm.com \
    --cc=arjanv@redhat.com \
    --cc=heicars2@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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

Powered by JetHome