netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [TCP] Modular IPv6 support in tcpdiag
Date: Thu, 4 Nov 2004 07:32:27 +1100	[thread overview]
Message-ID: <20041103203227.GA25279@gondor.apana.org.au> (raw)
In-Reply-To: <20041103091609.7f6d5d9c@zqx3.pdx.osdl.net>

On Wed, Nov 03, 2004 at 09:16:09AM -0800, Stephen Hemminger wrote:
> 
> I wanted to ask why all the work to make tcp_diag a module? If it is
> a module there are more possibilties of user problems. Any utilities
> that expect it would then have to deal with it not being loaded as well
> as the possiblity of building a kernel without it.

The reason is that prior to this if IPv6 was built as a module then
you couldn't have tcp_diag support for IPv6 sockets at all.

You're absolutely right about the potential problems with modules.
However, I did set the default to Y.

We should also have netlink module aliases so that these modules
can be loaded automatically by af_netlink.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2004-11-03 20:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03  9:44 [TCP] Modular IPv6 support in tcpdiag Herbert Xu
2004-11-03 11:26 ` YOSHIFUJI Hideaki / 吉藤英明
2004-11-03 17:16 ` Stephen Hemminger
2004-11-03 20:32   ` Herbert Xu [this message]
2004-11-03 20:20 ` David S. Miller
2004-11-03 20:34   ` Herbert Xu
2004-11-03 20:29     ` David S. Miller
2004-11-03 20:43       ` Herbert Xu
2004-11-03 20:41         ` David S. 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=20041103203227.GA25279@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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).