From: Nathan Scott <nscott@aconex.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: review: allocate bmapi args
Date: Thu, 19 Apr 2007 17:51:02 +1000 [thread overview]
Message-ID: <1176969062.6273.169.camel@edge> (raw)
In-Reply-To: <20070419072505.GS48531920@melbourne.sgi.com>
On Thu, 2007-04-19 at 17:25 +1000, David Chinner wrote:
>
> + bma = kmem_zalloc(sizeof(xfs_bmalloca_t), KM_SLEEP);
> + if (!bma)
> + return XFS_ERROR(ENOMEM);
I guess you meant KM_NOSLEEP? Are you sure this is legit though?
(are all callers going to be able to handle this?) I'm thinking
of the writeout paths where we're doing space allocation (unwritten
extent conversion comes through here too) in order to free up some
page cache so other memory allocs elsewhere can proceed. I don't
see any other memory allocations in this area of the code, so I
guess I'd be treading really carefully here..
(Oh, and why the _zalloc? Could just do an _alloc, since previous
code was using non-zeroed memory - so, should have been filling in
all fields).
cheers.
--
Nathan
next prev parent reply other threads:[~2007-04-19 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 7:25 review: allocate bmapi args David Chinner
2007-04-19 7:51 ` Nathan Scott [this message]
2007-04-19 8:23 ` David Chinner
2007-04-20 4:41 ` Nathan Scott
2007-04-20 5:34 ` David Chinner
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=1176969062.6273.169.camel@edge \
--to=nscott@aconex.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.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