From: Rik van Riel <riel@redhat.com>
To: rajman mekaco <rajman.mekaco@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
Christoph Lameter <cl@gentwo.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/1] mlock: split the shmlock_user_lock spinlock into per user_struct spinlock
Date: Thu, 03 May 2012 14:07:02 -0400 [thread overview]
Message-ID: <4FA2C946.60006@redhat.com> (raw)
In-Reply-To: <1336066477-3964-1-git-send-email-rajman.mekaco@gmail.com>
On 05/03/2012 01:34 PM, rajman mekaco wrote:
> The user_shm_lock and user_shm_unlock functions use a single global
> spinlock for protecting the user->locked_shm.
>
> This is an overhead for multiple CPUs calling this code even if they
> are having different user_struct.
>
> Remove the global shmlock_user_lock and introduce and use a new
> spinlock inside of the user_struct structure.
>
> Signed-off-by: rajman mekaco<rajman.mekaco@gmail.com>
Reviewed-by: Rik van Riel <riel@redhat.com>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: rajman mekaco <rajman.mekaco@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
Christoph Lameter <cl@gentwo.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/1] mlock: split the shmlock_user_lock spinlock into per user_struct spinlock
Date: Thu, 03 May 2012 14:07:02 -0400 [thread overview]
Message-ID: <4FA2C946.60006@redhat.com> (raw)
In-Reply-To: <1336066477-3964-1-git-send-email-rajman.mekaco@gmail.com>
On 05/03/2012 01:34 PM, rajman mekaco wrote:
> The user_shm_lock and user_shm_unlock functions use a single global
> spinlock for protecting the user->locked_shm.
>
> This is an overhead for multiple CPUs calling this code even if they
> are having different user_struct.
>
> Remove the global shmlock_user_lock and introduce and use a new
> spinlock inside of the user_struct structure.
>
> Signed-off-by: rajman mekaco<rajman.mekaco@gmail.com>
Reviewed-by: Rik van Riel <riel@redhat.com>
next prev parent reply other threads:[~2012-05-03 18:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:34 [PATCH 1/1] mlock: split the shmlock_user_lock spinlock into per user_struct spinlock rajman mekaco
2012-05-03 17:34 ` rajman mekaco
2012-05-03 18:07 ` Rik van Riel [this message]
2012-05-03 18:07 ` Rik van Riel
2012-05-03 20:27 ` Rik van Riel
2012-05-03 20:27 ` Rik van Riel
2012-05-04 1:12 ` rajman mekaco
2012-05-04 1:12 ` rajman mekaco
2012-05-10 13:34 ` rajman mekaco
2012-05-10 13:34 ` rajman mekaco
2012-05-10 14:54 ` Rik van Riel
2012-05-10 14:54 ` Rik van Riel
2012-05-10 15:39 ` rajman mekaco
2012-05-10 15:39 ` rajman mekaco
2012-05-10 16:48 ` rajman mekaco
2012-05-10 16:48 ` rajman mekaco
2012-05-10 22:30 ` Rik van Riel
2012-05-10 22:30 ` Rik van Riel
2012-05-12 3:10 ` rajman mekaco
2012-05-12 3:10 ` rajman mekaco
2012-05-03 19:31 ` Peter Zijlstra
2012-05-03 19:31 ` Peter Zijlstra
2012-05-03 20:26 ` Rik van Riel
2012-05-03 20:26 ` Rik van Riel
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=4FA2C946.60006@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rajman.mekaco@gmail.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.