From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Cong Wang <cwang@twopensource.com>
Cc: netdev <netdev@vger.kernel.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
"David S. Miller" <davem@davemloft.net>,
Thomas Graf <tgraf@suug.ch>
Subject: Re: [PATCH-next v2 3/4] net/sched: make sch_blackhole.c explicitly non-modular
Date: Thu, 8 Oct 2015 18:59:59 -0400 [thread overview]
Message-ID: <20151008225959.GN14103@windriver.com> (raw)
In-Reply-To: <CAHA+R7PgVBptnzzcWFW+9bp9UL40e+V+4K8PJjrF-KzeFQodQw@mail.gmail.com>
[Re: [PATCH-next v2 3/4] net/sched: make sch_blackhole.c explicitly non-modular] On 07/10/2015 (Wed 14:47) Cong Wang wrote:
> On Wed, Oct 7, 2015 at 2:27 PM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
> > The Kconfig currently controlling compilation of this code is:
> >
> > net/sched/Kconfig:menuconfig NET_SCHED
> > net/sched/Kconfig: bool "QoS and/or fair queueing"
> >
> > ...meaning that it currently is not being built as a module by anyone.
>
> Is there any reason why sch_blackhole can't be a module like
> other qdisc's?
>
> If not, I'd rather making it be a module. It is small but not often used.
As I've said in other similar threads, there are some 300+ places
where code that can't ever be modular uses modular calls and/or
introduces dead module remove code.
Hence here I am making the code consistent with its current limitations.
I'm not looking to extend functionality in code that I don't know
intimately. I can't do that and do it reliably and guarantee it
works as a module when it has never been used as such before in 300+
places all across the kernel.
If there are interested users who want their code tristate and can vouch
that their code works OK as such, I can drop the patch(es) here ; this
is what happened with 4 of the patches I originally had in v1 of this
very series. But a good number of the 300+ instances have been this way
since before git history began (2005) and so I wonder the value in say
extending instances like old ISA drivers from bool to tristate...
Paul.
--
next prev parent reply other threads:[~2015-10-08 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 21:27 [PATCH-next v2 0/4] make non-modular code explicitly non-modular Paul Gortmaker
2015-10-07 21:27 ` [PATCH-next v2 1/4] net/core: make sock_diag.c " Paul Gortmaker
2015-10-07 21:27 ` [PATCH-next v2 2/4] net/dcb: make dcbnl.c " Paul Gortmaker
2015-10-07 21:27 ` [PATCH-next v2 3/4] net/sched: make sch_blackhole.c " Paul Gortmaker
2015-10-07 21:47 ` Cong Wang
2015-10-08 22:59 ` Paul Gortmaker [this message]
2015-10-07 21:27 ` [PATCH-next v2 4/4] drivers/net/ethernet: make ti/cpsw-phy-sel.c " Paul Gortmaker
2015-10-09 14:52 ` [PATCH-next v2 0/4] make non-modular code " David Miller
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=20151008225959.GN14103@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).