linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: azurIt <azurit@pobox.sk>,
	linux-kernel@vger.kernel.org, Changli Gao <xiaosuo@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Eric Dumazet <eric.dumazet@gmail.com>,
	linux-fsdevel@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>
Subject: Re: Regression from 2.6.36
Date: Thu, 7 Apr 2011 19:21:00 +0800	[thread overview]
Message-ID: <BANLkTinnTnjZvQ9S1AmudZcZBokMy8-93w@mail.gmail.com> (raw)
In-Reply-To: <4D9D8FAA.9080405@suse.cz>

On Thu, Apr 7, 2011 at 6:19 PM, Jiri Slaby <jslaby@suse.cz> wrote:
> Cced few people.
>
> Also the series which introduced this were discussed at:
> http://lkml.org/lkml/2010/5/3/53
>

I guess this is due to that lots of fdt are allocated by kmalloc(),
not vmalloc(), and we kfree() them in rcu callback.

How about deferring all of the removal to workqueue? This may
hurt performance I think.

Anyway, like the patch below... makes sense?

Not-yet-signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>

---
diff --git a/fs/file.c b/fs/file.c
index 0be3447..34dc355 100644
--- a/fs/file.c
+++ b/fs/file.c
@@ -96,20 +96,14 @@ void free_fdtable_rcu(struct rcu_head *rcu)
                                container_of(fdt, struct files_struct, fdtab));
                return;
        }
-       if (!is_vmalloc_addr(fdt->fd) && !is_vmalloc_addr(fdt->open_fds)) {
-               kfree(fdt->fd);
-               kfree(fdt->open_fds);
-               kfree(fdt);
-       } else {
-               fddef = &get_cpu_var(fdtable_defer_list);
-               spin_lock(&fddef->lock);
-               fdt->next = fddef->next;
-               fddef->next = fdt;
-               /* vmallocs are handled from the workqueue context */
-               schedule_work(&fddef->wq);
-               spin_unlock(&fddef->lock);
-               put_cpu_var(fdtable_defer_list);
-       }
+
+       fddef = &get_cpu_var(fdtable_defer_list);
+       spin_lock(&fddef->lock);
+       fdt->next = fddef->next;
+       fddef->next = fdt;
+       schedule_work(&fddef->wq);
+       spin_unlock(&fddef->lock);
+       put_cpu_var(fdtable_defer_list);
 }

--
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>

  reply	other threads:[~2011-04-07 11:21 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110315132527.130FB80018F1@mail1005.cent>
     [not found] ` <20110317001519.GB18911@kroah.com>
     [not found]   ` <20110407120112.E08DCA03@pobox.sk>
2011-04-07 10:19     ` Regression from 2.6.36 Jiri Slaby
2011-04-07 11:21       ` Américo Wang [this message]
2011-04-07 11:57         ` Eric Dumazet
2011-04-07 12:13           ` Eric Dumazet
2011-04-07 15:27             ` Changli Gao
2011-04-07 15:36               ` Eric Dumazet
2011-04-12 22:49                 ` Andrew Morton
2011-04-13  1:23                   ` Changli Gao
2011-04-13  1:31                     ` Andrew Morton
2011-04-13  2:37                       ` Eric Dumazet
2011-04-13  6:54                         ` Regarding memory fragmentation using malloc Pintu Agarwal
2011-04-13 11:44                           ` Américo Wang
2011-04-13 13:56                             ` Pintu Agarwal
2011-04-13 15:25                               ` Michal Nazarewicz
2011-04-14  6:44                                 ` Pintu Agarwal
2011-04-14 10:47                                   ` Michal Nazarewicz
2011-04-14 12:24                                     ` Pintu Agarwal
2011-04-14 12:31                                       ` Michal Nazarewicz
2011-04-13 21:16                         ` Regression from 2.6.36 Andrew Morton
2011-04-13 21:24                           ` Andrew Morton
2011-04-19 19:29                             ` azurIt
2011-04-19 19:55                               ` Andrew Morton
2011-04-13 21:44                           ` David Rientjes
2011-04-13 21:54                             ` Andrew Morton
2011-04-14  2:10                           ` Eric Dumazet
2011-04-14  5:28                             ` Andrew Morton
2011-04-14  6:31                               ` Eric Dumazet
2011-04-14  9:08                                 ` azurIt
2011-04-14 10:27                                   ` Eric Dumazet
2011-04-14 10:31                                     ` azurIt
2011-04-14 10:25                           ` Mel Gorman
2011-04-15  9:59                             ` azurIt
2011-04-15 10:47                               ` Mel Gorman
2011-04-15 10:56                                 ` azurIt
2011-04-15 11:17                                   ` Mel Gorman
2011-04-15 11:36                                     ` azurIt
2011-04-15 13:01                                       ` Mel Gorman
2011-04-15 13:21                                         ` azurIt
2011-04-15 14:15                                           ` Mel Gorman
2011-04-08 12:25               ` azurIt

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=BANLkTinnTnjZvQ9S1AmudZcZBokMy8-93w@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=azurit@pobox.sk \
    --cc=eric.dumazet@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=xiaosuo@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 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).