From: Thomas Graf <tgraf@suug.ch>
To: "David S. Miller" <davem@davemloft.net>
Cc: kaber@trash.net, bunk@stusta.de, evil@g-house.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
zippel@linux-m68k.org
Subject: Re: [2.6 patch] do not select NET_CLS
Date: Wed, 23 Nov 2005 11:27:10 +0100 [thread overview]
Message-ID: <20051123102710.GH20395@postel.suug.ch> (raw)
In-Reply-To: <20051122.143713.101129339.davem@davemloft.net>
* David S. Miller <davem@davemloft.net> 2005-11-22 14:37
> From: Patrick McHardy <kaber@trash.net>
> Date: Mon, 21 Nov 2005 17:16:18 +0100
>
> > Adrian Bunk wrote:
> > > This patch therefore changes NET_CLS back to the 2.6.14 status quo of
> > > being an user-visible option.
> >
> > I disagree with this patch. NET_CLS enables the infrastructure support
> > for classifiers. Users generally don't care about infrastructure but
> > directly usable things, so I'd prefer to have it automatically selected.
> > And there are lots of other cases where enabling a module causes changes
> > in the kernel image. Some examples include some of the netfilter stuff,
> > the IPsec transforms, NET_CLS_ROUTE4, the ieee80211 stuff, and a lot
> > more.
>
> I agree with Patrick.
In fact Patrick's explanation was exactly the motivation for me to
change it in the first place a few weeks back.
I thought about making cls_api aware to be built as module but then
the same would apply for ematches and the generic scheduling code
and it gets real complicated. It is possible with some heavy code
shuffling but not worth it I think.
prev parent reply other threads:[~2005-11-23 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <437BBC59.70301@g-house.de>
2005-11-16 23:58 ` 2.6.15-rc1: NET_CLS_U32 not working? Adrian Bunk
2005-11-17 0:06 ` Christian
2005-11-17 15:57 ` Christian
2005-11-21 15:59 ` [2.6 patch] do not select NET_CLS Adrian Bunk
2005-11-21 16:16 ` Patrick McHardy
2005-11-22 22:37 ` David S. Miller
2005-11-22 22:49 ` Sam Ravnborg
2005-11-22 23:00 ` David S. Miller
2005-11-23 5:57 ` Sam Ravnborg
2005-11-24 2:13 ` Randy.Dunlap
2005-11-24 5:40 ` Sam Ravnborg
2005-11-22 23:12 ` Adrian Bunk
2005-11-23 10:27 ` Thomas Graf [this message]
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=20051123102710.GH20395@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=evil@g-house.de \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zippel@linux-m68k.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 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).