From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Bill Pemberton <wfp5p@virginia.edu>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 407/493] infiniband: remove use of __devexit
Date: Mon, 19 Nov 2012 15:00:06 -0800 [thread overview]
Message-ID: <20121119230006.GA2523@kroah.com> (raw)
In-Reply-To: <20121119224845.GB5636@obsidianresearch.com>
On Mon, Nov 19, 2012 at 03:48:45PM -0700, Jason Gunthorpe wrote:
> On Mon, Nov 19, 2012 at 02:06:32PM -0800, Greg KH wrote:
>
> > > 5k isn't a lot, but in the context of 'I have to figure out how to
> > > trim ~1MB off the 3.6 kernel to run it in our smallest hardware' it is
> > > the wrong direction :(
> >
> > It is only 0.138% in the "wrong" direction. Seriously, that's a very
> > tiny percentage here, for an option that people _always_ get wrong, and
> > almost no system does not need. The number of bugs we have had in this
> > area is huge, and by fixing this option like this, it takes them all
> > away.
>
> Sure, it isn't a lot. I don't have any idea about problems
> CONFIG_HOTPLUG causes, but it seems alot of work has gone into making
> this option over the years (the patch to remove it is huge), is there
> no other way to get what you want?
The patch overall, is only 7kb or so. It's the fact that it is just
removing the __dev* markings all over the tree that makes it so "big".
The big change is just in a very few places in the kernel core that
actually do something different depending on CONFIG_HOTPLUG or not.
I could just leave things alone, with CONFIG_HOTPLUG always enabled, but
then people will continue to blindly use the __dev* markings, getting it
wrong at times, but never realizing that they don't do anything anymore.
Because they don't do anything anymore, the right thing to do is just
remove them, which is what Bill's patches do.
Hope this helps explain things better.
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-19 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353349642-3677-1-git-send-email-wfp5p@virginia.edu>
[not found] ` <1353349642-3677-407-git-send-email-wfp5p@virginia.edu>
[not found] ` <20121119200921.GD1556@obsidianresearch.com>
[not found] ` <20121119201938.GA5614@kroah.com>
2012-11-19 21:49 ` [PATCH 407/493] infiniband: remove use of __devexit Jason Gunthorpe
2012-11-19 22:06 ` Greg KH
2012-11-19 22:48 ` Jason Gunthorpe
2012-11-19 23:00 ` Greg KH [this message]
2012-11-19 23:17 ` Jason Gunthorpe
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=20121119230006.GA2523@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=wfp5p@virginia.edu \
/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).