All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Subject: Re: [PATCH v2 0/2] Don't allocate ib/iw cm workqueues with WQ_MEM_RECLAIM
Date: Fri, 18 Aug 2017 10:48:53 -0400	[thread overview]
Message-ID: <1503067733.2598.8.camel@redhat.com> (raw)
In-Reply-To: <1502824838-21745-1-git-send-email-sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>

On Tue, 2017-08-15 at 22:20 +0300, Sagi Grimberg wrote:
> It's not correct due to the fact that such workqueues cannot allocate
> memory in their work execution by definition, which is definitly not
> the case for cm workqueues.
> 
> Changes from v1:
> - fixed spelling glitch
> 
> Sagi Grimberg (2):
>   cm: Don't allocate ib_cm workqueue with WQ_MEM_RECLAIM
>   iwcm: Don't allocate iwcm workqueue with WQ_MEM_RECLAIM
> 
>  drivers/infiniband/core/cm.c   | 2 +-
>  drivers/infiniband/core/iwcm.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Thanks Sagi, series applied.

-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2017-08-18 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 19:20 [PATCH v2 0/2] Don't allocate ib/iw cm workqueues with WQ_MEM_RECLAIM Sagi Grimberg
     [not found] ` <1502824838-21745-1-git-send-email-sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-08-15 19:20   ` [PATCH v2 1/2] cm: Don't allocate ib_cm workqueue " Sagi Grimberg
2017-08-15 19:20   ` [PATCH v2 2/2] iwcm: Don't allocate iwcm " Sagi Grimberg
2017-08-15 20:53   ` [PATCH v2 0/2] Don't allocate ib/iw cm workqueues " Parav Pandit
     [not found]     ` <VI1PR0502MB300859CC289623BEA5D2DF9AD18D0-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-08-15 20:56       ` Parav Pandit
2017-08-18 14:48   ` Doug Ledford [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=1503067733.2598.8.camel@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org \
    --cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
    /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.