mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: vandrove@vc.cvut.cz, vl@kki.org
Cc: linux-kernel@vger.kernel.org
Subject: [STACK] >3k call path in ncpfs
Date: Wed, 9 Jun 2004 14:20:02 +0200	[thread overview]
Message-ID: <20040609122002.GD21168@wohnheim.fh-wedel.de> (raw)

ncpfs has a few stack-hungry functions.  Could you try to put
ncp_ioctl() and/or ncp_conn_logged_in() on a diet?  Example call path
is below.

stackframes for call path too long (3004):
    size  function
     720  ncp_ioctl
     616  ncp_conn_logged_in
      24  ncp_lookup_volume
       0  ncp_request2
     164  sock_sendmsg
       0  wait_on_sync_kiocb
      84  schedule
      16  __put_task_struct
      20  audit_free
      36  audit_log_start
      16  __kmalloc
       0  __get_free_pages
      28  __alloc_pages
     284  try_to_free_pages
       0  out_of_memory
       0  mmput
      16  exit_aio
       0  __put_ioctx
      16  do_munmap
       0  split_vma
      36  vma_adjust
       0  fput
       0  __fput
       0  locks_remove_flock
      12  panic
       0  sys_sync
       0  sync_inodes
     308  sync_inodes_sb
       0  do_writepages
     128  mpage_writepages
       4  write_boundary_block
       0  ll_rw_block
      28  submit_bh
       0  bio_alloc
      88  mempool_alloc
     256  wakeup_bdflush
      20  pdflush_operation
       0  printk
       0  preempt_schedule
      84  schedule

Jörn

-- 
Time? What's that? Time is only worth what you do with it.
-- Theo de Raadt

             reply	other threads:[~2004-06-09 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 12:20 Jörn Engel [this message]
2004-06-09 18:15 ` Byron Stanoszek
2004-06-09 18:27   ` Jörn Engel
2004-06-09 18:31     ` Byron Stanoszek
2004-06-10  0:06 ` [PATCH] Decrease stack usage in ncpfs's ioctl (was Re: [STACK] >3k call path in ncpfs) Petr Vandrovec

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=20040609122002.GD21168@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    --cc=vl@kki.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®