From: Krishna Kumar <krkumar@us.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, netdev@oss.sgi.com
Subject: Re: O/M flags against 2.6.0-test1
Date: Wed, 23 Jul 2003 15:32:23 -0700 [thread overview]
Message-ID: <3F1F0CF7.5020909@us.ibm.com> (raw)
In-Reply-To: <20030723031351.4e9db07c.davem@redhat.com>
Hi Dave,
> 1) Remove "void *sysctl;" from ipv6_devconf, move it into
> inet6_dev ie. "void *cnf_sysctl;" update all code users.
There is one problem with this that I am not able to figure out, perhaps I am
overlooking it. addrconf_sysctl_register() gets called for ipv6_devconf_dflt,
but there is no inet6_dev for this configuration, so is it possible to move the
sysctl up (there is no 'up' :-). I don't want to create a dummy inet6_dev for
this. One way is to embed the actual config structure as follows :
struct ipv6_devconf {
void *sysctl;
struct {
forwarding;
hop_limit;
...
} u;
};
and follow it up with #defines for all the elements, etc. Then I can use
sizeof(ipv6_devconf.u) without this problem. Another way to do this is using
pointer arithmetic :
RTA_PUT(skb, IFLA_INET6_CONF, &idev->cnf.sysctl-&idev->cnf.forwarding,
&idev->cnf);
(guess you may not like it based on your statement "pointers in it which makes
usage sloppy").
I also noticed there is no sysctl_register for ipv6_devconf, but there is a
unregister for that conf. Is that correct ?
> 2) Move "struct ipv6_devconf" into some linux/*.h ipv6 header
> usable by users. Use an existing one if possible. Then
> make sure net/if_inet6.h includes this thing.
The only two ipv6 specific files in linux are ipv6.h and ipv6_route.h, neither
are appropriate for sysctl stuff I think. So should I create a new file like the
one for ipv4_devconf exists in inetdevice.h ?
> 3) Change "int" members of struct "ipv6_devconf" to "s32".
All members (except use_tempaddr) seem to be >=0, should I change the definition
to __u32 instead ? I am OK either way, just wondering which is the right way to
do this.
Thanks,
- KK
next prev parent reply other threads:[~2003-07-23 22:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 22:35 [PATCH 1/4] Prefix List against 2.5.73 Krishna Kumar
2003-07-15 1:17 ` kuznet
2003-07-15 6:59 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-15 13:20 ` kuznet
2003-07-15 18:34 ` Krishna Kumar
2003-07-16 0:11 ` Krishna Kumar
2003-07-16 0:21 ` kuznet
2003-07-16 8:39 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-16 18:42 ` [PATCH 1/2] " Krishna Kumar
2003-07-16 18:49 ` Krishna Kumar
2003-07-16 18:50 ` [PATCH 2/2] Prefix List against 2.4.21 Krishna Kumar
2003-07-16 23:41 ` [PATCH 1/4] Prefix List against 2.5.73 kuznet
2003-07-17 0:06 ` Krishna Kumar
2003-07-17 0:38 ` kuznet
2003-07-17 21:12 ` [PATCH 1/2] Prefix List and O/M flags " Krishna Kumar
2003-07-17 22:06 ` [PATCH 2/2] Prefix List and O/M flags against 2.4.21 Krishna Kumar
2003-07-17 22:22 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-17 22:34 ` Krishna Kumar
2003-07-17 22:47 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-18 0:37 ` [PATCH 2/2] Prefix List and O/M flags against 2.5.73 Krishna Kumar
2003-07-19 6:47 ` David S. Miller
2003-07-19 7:33 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-21 0:49 ` kuznet
2003-07-21 12:17 ` David S. Miller
2003-07-21 17:16 ` Krishna Kumar
2003-07-21 1:55 ` [PATCH 2/2] Prefix List and O/M flags against 2.4.21 kuznet
2003-07-21 4:46 ` David S. Miller
2003-07-22 21:50 ` O/M flags against 2.6.0-test1 Krishna Kumar
2003-07-22 22:25 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-22 22:59 ` Krishna Kumar
2003-07-23 10:13 ` David S. Miller
2003-07-23 22:32 ` Krishna Kumar [this message]
2003-07-24 7:07 ` David S. Miller
2003-07-24 14:02 ` kuznet
2003-07-24 14:26 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-24 14:43 ` kuznet
2003-07-25 0:14 ` Krishna Kumar
2003-07-25 13:22 ` David S. Miller
2003-07-30 0:33 ` Krishna Kumar
2003-07-31 5:02 ` David S. Miller
2003-07-31 20:33 ` Krishna Kumar
2003-08-04 23:57 ` David S. Miller
2003-09-05 18:26 ` Krishna Kumar
2003-09-12 2:25 ` David S. Miller
2003-09-12 22:36 ` Krishna Kumar
2003-09-12 22:45 ` O/M flags for 2.4.22 (was "Re: O/M flags against 2.6.0-test1") Krishna Kumar
2003-09-13 0:19 ` David S. Miller
2003-09-16 22:06 ` Krishna Kumar
2003-09-20 8:18 ` David S. Miller
2003-07-22 23:52 ` [PATCH] Prefix List against 2.4.21 Krishna Kumar
2003-07-23 10:02 ` David S. Miller
2003-07-17 21:53 ` [PATCH 1/4] Prefix List against 2.5.73 YOSHIFUJI Hideaki / 吉藤英明
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=3F1F0CF7.5020909@us.ibm.com \
--to=krkumar@us.ibm.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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).