All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Bagalkote, Sreenivas" <sreenib@lsil.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.6.11-mm3: megaraid_sas.c: stack usage
Date: Tue, 31 May 2005 02:23:15 +0200	[thread overview]
Message-ID: <20050531002315.GF3627@stusta.de> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570230CC3D@exa-atlanta>

On Tue, Mar 15, 2005 at 10:13:17AM -0500, Bagalkote, Sreenivas wrote:
> >On Sat, Mar 12, 2005 at 03:42:22AM -0800, Andrew Morton wrote:
> >>...
> >> All 606 patches:
> >>...
> >> megaraid_sas-announcing-new-module-for.patch
> >>   megaraid_sas: Announcing new module for LSI Logic's SAS 
> >based MegaRAID controllers
> >>...
> >
> >Enormous stack usage:
> >- megasas_init_mfi (due to ctrl_info)
> >
> >Big stack usage:
> >- megasas_mgmt_ioctl (due to uioc and dv)
> >- megasas_mgmt_fw_ioctl (due to uioc)
> >
> >Please fix this.
> 
> Will do.

This issue is still present in 2.6.12-rc5-mm1.
Please fix at least the megasas_init_mfi stack usage.

> Thanks,
> Sreenivas

TIA
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-05-31  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 15:13 2.6.11-mm3: megaraid_sas.c: stack usage Bagalkote, Sreenivas
2005-05-31  0:23 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-12 11:42 2.6.11-mm3 Andrew Morton
2005-03-15 15:06 ` 2.6.11-mm3: megaraid_sas.c: stack usage Adrian Bunk

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=20050531002315.GF3627@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sreenib@lsil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.