[Top] [All Lists]

Re: [PATCH] anycast support for IPv6, updated to 2.5.44

To: yoshfuji@xxxxxxxxxx
Subject: Re: [PATCH] anycast support for IPv6, updated to 2.5.44
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Wed, 19 Mar 2003 19:23:31 -0800 (PST)
Cc: dlstevens@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20030320.120136.108400165.yoshfuji@xxxxxxxxxx>
References: <OFC909BFEE.F581E26E-ON88256C60.0072A662@xxxxxxxxxxxxxxx> <20030319.163105.44963500.davem@xxxxxxxxxx> <20030320.120136.108400165.yoshfuji@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
   From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxx>
   Date: Thu, 20 Mar 2003 12:01:36 +0900 (JST)

   In article <20030319.163105.44963500.davem@xxxxxxxxxx> (at Wed, 19 Mar 2003 
16:31:05 -0800 (PST)), "David S. Miller" <davem@xxxxxxxxxx> says:
   > I'm going to apply this, with the small change that dev_getany() is
   > renamed to dev_get_by_flags() which more accurately describes
   > what the routine does.
   Again: I don't like API at all.
   Anycast address management itself in that patch would be ok.
   However, JOIN/LEAVE is NOT useful and userland application will be 
   incompatible with other implementation. (sigh...)
   I think linux likes unicast model (assign address like unicast address), too.
Please propose alternative API, or do you suggest not
to export this facility to user at all?

   And, we see __constant_{hton,ntoh}{l,h}() again...
I will fix this, thank you for mentioning this.

<Prev in Thread] Current Thread [Next in Thread>