From: "ira.weiny" <ira.weiny@intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Saurabh Sengar <saurabh.truth@gmail.com>,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, yun.wang@profitbricks.com,
kaike.wan@intel.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/sa: replace GFP_KERNEL with GFP_ATOMIC
Date: Tue, 27 Oct 2015 14:20:42 -0400 [thread overview]
Message-ID: <20151027182041.GA32118@phlsvsds.ph.intel.com> (raw)
In-Reply-To: <20151027181652.GA6879@obsidianresearch.com>
On Tue, Oct 27, 2015 at 12:16:52PM -0600, Jason Gunthorpe wrote:
> On Tue, Oct 27, 2015 at 02:12:36PM -0400, ira.weiny wrote:
> > On Tue, Oct 27, 2015 at 09:17:40PM +0530, Saurabh Sengar wrote:
> > > replace GFP_KERNEL with GFP_ATOMIC, as code while holding a spinlock
> > > should be atomic
> > > GFP_KERNEL may sleep and can cause deadlock, where as GFP_ATOMIC may
> > > fail but certainly avoids deadlock
> >
> > Great catch. Thanks!
> >
> > However, gfp_t is passed to send_mad and we should pass that down and use it.
>
> > spin_lock_irqsave(&ib_nl_request_lock, flags);
> > - ret = ib_nl_send_msg(query);
> > + ret = ib_nl_send_msg(query, gfp_mask);
>
> A spin lock is guarenteed held around ib_nl_send_msg, so it's
> allocations have to be atomic, can't use gfp_mask here..
>
> I do wonder if it is a good idea to call ib_nl_send_msg with a spinlock
> held though.. Would be nice to see that go away.
Ah, yea my bad.
Ira
>
> Jason
next prev parent reply other threads:[~2015-10-27 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:47 Saurabh Sengar
2015-10-27 18:12 ` ira.weiny
2015-10-27 18:16 ` Jason Gunthorpe
2015-10-27 18:20 ` ira.weiny [this message]
2015-10-27 18:56 ` Wan, Kaike
2015-10-27 20:00 ` Jason Gunthorpe
2015-10-28 4:30 ` Weiny, Ira
2015-11-13 7:42 ` Saurabh Sengar
2015-11-13 10:47 ` Wan, Kaike
2015-11-13 12:37 ` Saurabh Sengar
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=20151027182041.GA32118@phlsvsds.ph.intel.com \
--to=ira.weiny@intel.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kaike.wan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=saurabh.truth@gmail.com \
--cc=sean.hefty@intel.com \
--cc=yun.wang@profitbricks.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
Powered by JetHome