From: Theodore Ts'o <tytso@mit.edu>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] No more module removal -- Unconference track
Date: Wed, 27 Aug 2014 19:05:27 -0400 [thread overview]
Message-ID: <20140827230527.GX11317@thunk.org> (raw)
In-Reply-To: <53FC1A11.1000700@hitachi.com>
On Tue, Aug 26, 2014 at 02:24:33PM +0900, Masami Hiramatsu wrote:
> There could be. However, in usual usecases, I guess people will not want
> to unload it. Systemtap or something "additional" module users will
> need to unload modules. (kpatch could be one of them, but I also think
> no one want to remove applied patches anyway.)
>
> I just tried to show that the kmodule unload is the one who uses
> stop_machine heavily but it is not necessary :)
Right, but if the argument that kmodule unload is slow on huge NUMA
machines is that Rusty submits a patch which gets rid of the support
for module unload entirely, then that would be very sad. (And
**really** screw over systemtap...)
- Ted
next prev parent reply other threads:[~2014-08-27 23:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 14:48 Theodore Ts'o
2014-08-19 14:55 ` Guenter Roeck
2014-08-19 15:23 ` Theodore Ts'o
2014-08-19 15:40 ` Dan Carpenter
2014-08-19 15:47 ` Guenter Roeck
2014-08-19 16:09 ` Dan Carpenter
2014-08-19 16:34 ` Martin K. Petersen
2014-08-19 16:59 ` Rik van Riel
2014-08-19 17:19 ` Guenter Roeck
2014-08-19 16:43 ` David Woodhouse
2014-08-19 17:13 ` Grant Likely
2014-08-19 17:23 ` David Woodhouse
2014-08-19 15:54 ` Takashi Iwai
2014-08-25 11:01 ` Masami Hiramatsu
2014-08-25 11:05 ` Jiri Kosina
2014-08-26 5:24 ` Masami Hiramatsu
2014-08-27 23:05 ` Theodore Ts'o [this message]
2014-08-26 21:39 ` David Howells
2014-08-26 21:45 ` Jiri Kosina
2014-08-27 6:43 ` Masami Hiramatsu
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=20140827230527.GX11317@thunk.org \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=masami.hiramatsu.pt@hitachi.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