From: Arjan van de Ven <arjan@infradead.org>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to safely reduce stack usage in nfs code?
Date: Fri, 29 Oct 2004 11:01:41 +0200 [thread overview]
Message-ID: <1099040501.2641.9.camel@laptop.fenrus.org> (raw)
In-Reply-To: <200410290020.01400.vda@port.imtp.ilyichevsk.odessa.ua>
On Fri, 2004-10-29 at 00:20 +0300, Denis Vlasenko wrote:
> I can convert these into kmalloc'ed variants but hesitate to do so
> because of possible 'need to kmalloc in order to free memory for kmalloc'
> deadlocks.
how about a memory pool?
It's not THE solution but I suspect the depth of callchains of these isn't too deep so it would work
next prev parent reply other threads:[~2004-10-29 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 21:20 Denis Vlasenko
2004-10-29 0:15 ` Andreas Dilger
2004-10-29 9:01 ` Arjan van de Ven [this message]
2004-10-29 14:20 ` Trond Myklebust
2004-10-29 21:59 ` [PATCH] reduce stack usage of NFS (was Re: How to safely reduce...) Denis Vlasenko
2004-10-30 3:01 ` Randy.Dunlap
2004-10-30 9:23 ` Denis Vlasenko
2004-11-01 20:57 ` Trond Myklebust
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=1099040501.2641.9.camel@laptop.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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