From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] 2.4 and stack reduction patches
Date: Sat, 08 Jan 2005 23:08:15 -0500 [thread overview]
Message-ID: <1105243695.17456.0.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1105145706.4000.123.camel@dyn318077bld.beaverton.ibm.com>
fr den 07.01.2005 Klokka 16:55 (-0800) skreiv Badari Pulavarty:
> On Fri, 2005-01-07 at 14:40, Trond Myklebust wrote:
>
> >
> > You're better off using rpc_new_task() in rpc_call_sync(): no kfree()
> > required, and no rpc_init_task() required.
> >
>
> Hmm.. I am trying to do this. Just wanted to double check.
>
> If I don't do kfree(), its gets automatically freed up thro
> rpc_release_task() correct ?
Yes.
--
Trond Myklebust <trond.myklebust@fys.uio.no>
next prev parent reply other threads:[~2005-01-09 4:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 15:48 [RFC] 2.4 and stack reduction patches Badari Pulavarty
2005-01-07 14:12 ` Marcelo Tosatti
2005-01-07 21:42 ` Badari Pulavarty
2005-01-07 22:40 ` Trond Myklebust
2005-01-07 22:50 ` Badari Pulavarty
2005-01-08 0:55 ` Badari Pulavarty
2005-01-09 4:08 ` Trond Myklebust [this message]
2005-01-08 21:34 ` Denis Vlasenko
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=1105243695.17456.0.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=pbadari@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).