linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: green@linuxhacker.ru
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Oleg Drokin <green@linuxhacker.ru>
Subject: [PATCH 0/2] Export __vmalloc_node symbol
Date: Sun,  1 Feb 2015 22:10:25 -0500	[thread overview]
Message-ID: <1422846627-26890-1-git-send-email-green@linuxhacker.ru> (raw)

From: Oleg Drokin <green@linuxhacker.ru>

Looking to get rid of a deadlock in Lustre where vmalloc call recurses
right back into Lustre to free some memory due to not accepting GFP mask
I noticed that while vzalloc is replaceable with __vmalloc just as
suggested, vzalloc_node is not. Recommended __vmalloc_node symbol is
static to mm/vmalloc.c.
Hopefully nobody has any objections to me exporting it so that
vzalloc_node suggestion actually becomes possible.

Second patch in the series is just a Lustre patch to take advantage
of that newly exported symbol (as an example of usage).

Please consider.

Bruno Faccini (1):
  staging/lustre: use __vmalloc_node() to avoid __GFP_FS default

Oleg Drokin (1):
  mm: Export __vmalloc_node

 drivers/staging/lustre/lustre/include/obd_support.h | 18 ++++++++++++------
 include/linux/vmalloc.h                             |  3 +++
 mm/vmalloc.c                                        | 10 ++++------
 3 files changed, 19 insertions(+), 12 deletions(-)

-- 
2.1.0

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2015-02-02  3:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02  3:10 green [this message]
2015-02-02  3:10 ` [PATCH 1/2] mm: Export __vmalloc_node green
2015-02-02 17:45   ` David Rientjes
2015-02-02 20:31     ` Oleg Drokin
2015-02-02  3:10 ` [PATCH 2/2] staging/lustre: use __vmalloc_node() to avoid __GFP_FS default green
2015-02-02 17:48   ` David Rientjes
2015-02-02 23:26     ` Oleg Drokin

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=1422846627-26890-1-git-send-email-green@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.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 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).