All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging/lustre: Always try kmalloc first for OBD_ALLOC_LARGE
Date: Sun, 03 May 2015 19:44:03 +0000	[thread overview]
Message-ID: <20150503194403.GA24491@kroah.com> (raw)
In-Reply-To: <1430625501-1069-1-git-send-email-green@linuxhacker.ru>

On Sun, May 03, 2015 at 03:14:58PM -0400, Oleg Drokin wrote:
> Hello!
> 
> On May 3, 2015, at 2:31 PM, Greg KH wrote:
> 
> >> -/* Allocations above this size are considered too big and could not be done
> >> - * atomically.
> >> - *
> >> - * Be very careful when changing this value, especially when decreasing it,
> >> - * since vmalloc in Linux doesn't perform well on multi-cores system, calling
> >> - * vmalloc in critical path would hurt performance badly. See LU-66.
> >> - */
> >> -#define OBD_ALLOC_BIG (4 * PAGE_CACHE_SIZE)
> >> -
> >> #define OBD_ALLOC_LARGE(ptr, size)					    \
> >> do {									  \
> >> -	if (size > OBD_ALLOC_BIG)					     \
> >> -		OBD_VMALLOC(ptr, size);				       \
> >> -	else								  \
> >> -		OBD_ALLOC(ptr, size);					 \
> >> +	ptr = libcfs_kvzalloc(size, GFP_NOFS);				  \
> >> } while (0)
> > 
> > Just fix up all callers of these functions, if there are any anymore.
> 
> This is what Julia is doing. I am providing the stub for her wonderful scripts to unwrap per her request.
> 
> >> + */
> >> +/*
> >> + * Copyright (c) 2015, Oleg Drokin <green@linuxhacker.ru>
> > 
> > I think your employer would like a different line here...
> 
> Only on stuff that I do at work when I am getting paid.
> 
> Stuff that I do on my own uncompensated, I own all the rights to, I hope.

I wouldn't be so sure about this, please read your employment contract,
almost no companies allow this, it is very rare.

thanks,

greg k-h

  parent reply	other threads:[~2015-05-03 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-03  3:58 [PATCH] staging/lustre: Always try kmalloc first for OBD_ALLOC_LARGE green
2015-05-03 18:31 ` Greg KH
2015-05-03 19:14 ` Oleg Drokin
2015-05-03 19:44 ` Greg KH [this message]
2015-05-04 16:48 ` green

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=20150503194403.GA24491@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-janitors@vger.kernel.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.