All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <minggr@gmail.com>
To: lkp@lists.01.org
Subject: Re: increased vmap_area_lock contentions on "n_tty: Move buffers into n_tty_data"
Date: Thu, 26 Sep 2013 00:02:24 +0800	[thread overview]
Message-ID: <1380124944.27676.1.camel@monkey32> (raw)
In-Reply-To: <5242C960.7050506@hurleysoftware.com>

[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]

On Wed, 2013-09-25 at 07:30 -0400, Peter Hurley wrote:
> On 09/25/2013 05:04 AM, Lin Ming wrote:
> > On Wed, Sep 18, 2013 at 8:22 AM, Peter Hurley <peter@hurleysoftware.com> wrote:
> > [snip]
> >>
> >> Looking over vmalloc.c, the critical section footprint of the vmap_area_lock
> >> could definitely be reduced (even nearly eliminated), but that's a project
> >> for
> >> another day :)
> >
> > Hi Peter,
> >
> > I also looked over vmallo.c, but didn't find obvious way to reduce the
> > critical section footprint.
> > Could you share some hints how to do this?
> 
> vmap_area_list is an RCU list.
> get_vmalloc_info() doesn't need to take the vmap_area_lock at all.
> Look at __purge_vmap_area_lazy() for a howto.

Would you like below patch?

From: Lin Ming <minggr@gmail.com>
Date: Wed, 25 Sep 2013 23:48:19 +0800
Subject: [PATCH] mm/vmalloc.c: eliminate vmap_area_lock in get_vmalloc_info()

vmap_area_list is an RCU list.
get_vmalloc_info() doesn't need to take the vmap_area_lock at all.
Use RCU to protect list scan.

Signed-off-by: Lin Ming <minggr@gmail.com>
---
 mm/vmalloc.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 13a5495..4523c9c 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -2684,14 +2684,14 @@ void get_vmalloc_info(struct vmalloc_info *vmi)
 
 	prev_end = VMALLOC_START;
 
-	spin_lock(&vmap_area_lock);
+	rcu_read_lock();
 
 	if (list_empty(&vmap_area_list)) {
 		vmi->largest_chunk = VMALLOC_TOTAL;
 		goto out;
 	}
 
-	list_for_each_entry(va, &vmap_area_list, list) {
+	list_for_each_entry_rcu(va, &vmap_area_list, list) {
 		unsigned long addr = va->va_start;
 
 		/*
@@ -2718,7 +2718,7 @@ void get_vmalloc_info(struct vmalloc_info *vmi)
 		vmi->largest_chunk = VMALLOC_END - prev_end;
 
 out:
-	spin_unlock(&vmap_area_lock);
+	rcu_read_unlock();
 }
 #endif
 
-- 
1.7.2.5



> 
> Regards,
> Peter Hurley
> 



WARNING: multiple messages have this Message-ID (diff)
From: Lin Ming <minggr@gmail.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org, Tejun Heo <tj@kernel.org>
Subject: Re: increased vmap_area_lock contentions on "n_tty: Move buffers into n_tty_data"
Date: Thu, 26 Sep 2013 00:02:24 +0800	[thread overview]
Message-ID: <1380124944.27676.1.camel@monkey32> (raw)
In-Reply-To: <5242C960.7050506@hurleysoftware.com>

On Wed, 2013-09-25 at 07:30 -0400, Peter Hurley wrote:
> On 09/25/2013 05:04 AM, Lin Ming wrote:
> > On Wed, Sep 18, 2013 at 8:22 AM, Peter Hurley <peter@hurleysoftware.com> wrote:
> > [snip]
> >>
> >> Looking over vmalloc.c, the critical section footprint of the vmap_area_lock
> >> could definitely be reduced (even nearly eliminated), but that's a project
> >> for
> >> another day :)
> >
> > Hi Peter,
> >
> > I also looked over vmallo.c, but didn't find obvious way to reduce the
> > critical section footprint.
> > Could you share some hints how to do this?
> 
> vmap_area_list is an RCU list.
> get_vmalloc_info() doesn't need to take the vmap_area_lock at all.
> Look at __purge_vmap_area_lazy() for a howto.

Would you like below patch?

From: Lin Ming <minggr@gmail.com>
Date: Wed, 25 Sep 2013 23:48:19 +0800
Subject: [PATCH] mm/vmalloc.c: eliminate vmap_area_lock in get_vmalloc_info()

vmap_area_list is an RCU list.
get_vmalloc_info() doesn't need to take the vmap_area_lock at all.
Use RCU to protect list scan.

Signed-off-by: Lin Ming <minggr@gmail.com>
---
 mm/vmalloc.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 13a5495..4523c9c 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -2684,14 +2684,14 @@ void get_vmalloc_info(struct vmalloc_info *vmi)
 
 	prev_end = VMALLOC_START;
 
-	spin_lock(&vmap_area_lock);
+	rcu_read_lock();
 
 	if (list_empty(&vmap_area_list)) {
 		vmi->largest_chunk = VMALLOC_TOTAL;
 		goto out;
 	}
 
-	list_for_each_entry(va, &vmap_area_list, list) {
+	list_for_each_entry_rcu(va, &vmap_area_list, list) {
 		unsigned long addr = va->va_start;
 
 		/*
@@ -2718,7 +2718,7 @@ void get_vmalloc_info(struct vmalloc_info *vmi)
 		vmi->largest_chunk = VMALLOC_END - prev_end;
 
 out:
-	spin_unlock(&vmap_area_lock);
+	rcu_read_unlock();
 }
 #endif
 
-- 
1.7.2.5



> 
> Regards,
> Peter Hurley
> 



  parent reply	other threads:[~2013-09-25 16:02 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13  0:51 increased vmap_area_lock contentions on "n_tty: Move buffers into n_tty_data" Fengguang Wu
2013-09-13  0:51 ` Fengguang Wu
2013-09-13  1:09 ` Fengguang Wu
2013-09-13  1:09   ` Fengguang Wu
2013-09-17 15:34   ` Peter Hurley
2013-09-17 15:34     ` Peter Hurley
2013-09-17 23:22     ` Fengguang Wu
2013-09-17 23:22       ` Fengguang Wu
2013-09-18  0:22       ` Peter Hurley
2013-09-18  0:22         ` Peter Hurley
2013-09-25  9:04         ` Lin Ming
2013-09-25  9:04           ` Lin Ming
2013-09-25 11:30           ` Peter Hurley
2013-09-25 11:30             ` Peter Hurley
2013-09-25 14:53             ` Lin Ming
2013-09-25 14:53               ` Lin Ming
2013-09-25 16:02             ` Lin Ming [this message]
2013-09-25 16:02               ` Lin Ming
2013-09-26  3:20               ` Andi Kleen
2013-09-26  3:20                 ` Andi Kleen
2013-09-26 11:52                 ` Peter Hurley
2013-09-26 11:52                   ` Peter Hurley
2013-09-26 15:32                   ` Andi Kleen
2013-09-26 15:32                     ` Andi Kleen
2013-09-26 17:22                     ` Peter Hurley
2013-09-26 17:22                       ` Peter Hurley
2013-09-26  7:33         ` Andrew Morton
2013-09-26  7:33           ` Andrew Morton
2013-09-26 11:31           ` Peter Hurley
2013-09-26 11:31             ` Peter Hurley
2013-09-26 15:04             ` Greg KH
2013-09-26 15:04               ` Greg KH
2013-09-26 17:35               ` Peter Hurley
2013-09-26 17:35                 ` Peter Hurley
2013-09-26 18:05                 ` Andrew Morton
2013-09-26 18:05                   ` Andrew Morton
2013-09-26 21:42                   ` Peter Hurley
2013-09-26 21:42                     ` Peter Hurley
2013-09-26 21:58                     ` Andrew Morton
2013-09-26 21:58                       ` Andrew Morton
2013-09-26 22:21                       ` Peter Hurley
2013-09-26 22:21                         ` Peter Hurley
2013-09-18  0:49   ` Peter Hurley
2013-09-18  0:49     ` Peter Hurley
2013-09-13  3:17 ` Greg KH
2013-09-13  3:17   ` Greg KH
2013-09-13  3:38   ` Fengguang Wu
2013-09-13  3:38     ` Fengguang Wu
2013-09-13  3:44     ` Greg KH
2013-09-13  3:44       ` Greg KH
2013-09-13  9:55       ` Peter Hurley
2013-09-13  9:55         ` Peter Hurley
2013-09-13 12:34         ` Greg KH
2013-09-13 12:34           ` Greg KH
2013-09-17  2:42     ` Peter Hurley
2013-09-17  2:42       ` Peter Hurley
2013-09-17  2:56       ` Fengguang Wu
2013-09-17  2:56         ` Fengguang Wu

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=1380124944.27676.1.camel@monkey32 \
    --to=minggr@gmail.com \
    --cc=lkp@lists.01.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.