Re: v2.6 IGMPv3 implementation

[YOSHIFUJI Hideaki / 吉藤英明]

In article <20040713012152.GL7822@xxxxxxxxxxxxxxxxx> (at Mon, 12 Jul 2004 21:21:52 -0400), "Charles R. Anderson" <cra@xxxxxxx> says:

> On Tue, Jul 13, 2004 at 06:22:26AM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> > These ioctls are "historic" and deprecated API.
> > So, just kill them to avoid confusion.
> > We use socket options.
> 
> Thank you.  I have now read RFC3678 carefully and I have more
> questions.  The kernel still declares the structs used for these
> obsolete ioctls, but instead defines sockoptions for them:
:
> Is it intended that glibc use these sockoptions internally for its
> implementation of the approved Advanced API functions, which are then
> exported to user programs:
> 
> setipv4sourcefilter()
> getipv4sourcefilter()
> setsourcefilter()
> getsourcefilter()

Yes.

> Does the following limitation from RFC3678 Appendix A (rationale for
> the ioctl interface) apply to the Linux kernel getsockopt(), or can

No, so we can do both (set/get) by sockopt.

--yoshfuji
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/