From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2/dlmfs: use GFP_KERNEL instead of GFP_NOFS
Date: Wed, 17 Nov 2010 15:29:23 -0800 [thread overview]
Message-ID: <20101117232923.GH25677@mail.oracle.com> (raw)
In-Reply-To: <20101117011235.GA2289@laptop.jp.oracle.com>
On Wed, Nov 17, 2010 at 09:12:35AM +0800, Wengang Wang wrote:
> On 10-11-16 09:19, Sunil Mushran wrote:
> > We do NOFS allocs in the dlm to prevent deadlocks (not live locks).
> > And you are right we don't have to do NOFS allocs here. But the sizes
> > we are talking about are really small. Do we really care?
>
> I didn't hit problem at the allocation with NOFS.
> I just noticed it when looking at the codes.
> Since the sizes are small, it shouldn't effects much.
I'm going to vote -EDONTCARE.
Joel
--
"Friends may come and go, but enemies accumulate."
- Thomas Jones
Joel Becker
Senior Development Manager
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2010-11-17 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 15:33 [Ocfs2-devel] [PATCH] ocfs2/dlmfs: use GFP_KERNEL instead of GFP_NOFS Wengang Wang
2010-11-16 17:19 ` Sunil Mushran
2010-11-17 1:12 ` Wengang Wang
2010-11-17 23:29 ` Joel Becker [this message]
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=20101117232923.GH25677@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.