mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	InterMezzo Development List 
	<intermezzo-devel@lists.sourceforge.net>
Subject: Re: top stack (l)users for 2.5.67
Date: Mon, 14 Apr 2003 13:18:52 -0600	[thread overview]
Message-ID: <20030414131852.I26054@schatzie.adilger.int> (raw)
In-Reply-To: <20030414190514.GB12740@wohnheim.fh-wedel.de>; from joern@wohnheim.fh-wedel.de on Mon, Apr 14, 2003 at 09:05:14PM +0200

On Apr 14, 2003  21:05 +0200, Jörn Engel wrote:
> On Mon, 14 April 2003 19:25:53 +0100, Dave Jones wrote:
> > On Mon, Apr 14, 2003 at 07:46:45PM +0200, J?rn Engel wrote:
> >  > +/* FIXME: should the below go into some header file? */
> >  > +#define PRESTO_COPY_KML_TAIL_BUFSIZE 4096
> >  >  struct file * presto_copy_kml_tail(struct presto_file_set *fset,
> >  >                                     unsigned long int start)
> >  >  {
> > 
> > so, presto_copy_kml_tail() is only called from
> > presto_finish_kml_truncate(), which doesn't seem to be called
> > from anywhere. What am I missing here? Or can this whole lot
> > just be nuked ?
> 
> No idea. I'm just trying to get the kernel into a state where the
> kernel stack can be reduced to 4k relatively safely.
> As far as intermezzo is concerned, I've never even heard of someone
> using it and care accordingly.
> 
> > If not, this patch introduces a problem.  You're now
> > calling a sleeping function (kmalloc) whilst holding
> > a lock according to the comment above presto_finish_kml_truncate()
> 
> Ack. Would it be ok to malloc with GFP_ATOMIC then, or would you
> propose something different?

I've CC'd the InterMezzo mailing list (which is where the maintainers of
this code live).  Could someone please post a copy of the original patch
to the intermezzo-devel@lists.sourceforge.net mailing list?

Actually, my recollection is that there was previously a patch posted
for fixing this large stack usage the last time this came up.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2003-04-14 19:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 17:30 Jörn Engel
2003-04-14 16:37 ` Alan Cox
2003-04-14 17:46   ` Jörn Engel
2003-04-14 18:25     ` Dave Jones
2003-04-14 19:05       ` Jörn Engel
2003-04-14 19:18         ` Andreas Dilger [this message]
2003-04-14 19:40           ` Jörn Engel
2003-04-15 15:38             ` Peter Braam
2003-04-15  9:08               ` Jörn Engel
2003-04-14 19:38 ` Randy.Dunlap
2003-04-14 19:44   ` Jörn Engel

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=20030414131852.I26054@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=intermezzo-devel@lists.sourceforge.net \
    --cc=joern@wohnheim.fh-wedel.de \
    --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®