From: kuznet@ms2.inr.ac.ru
To: davem@redhat.com (David S. Miller)
Cc: krkumar@us.ibm.com, yoshfuji@linux-ipv6.org, netdev@oss.sgi.com
Subject: Re: O/M flags against 2.6.0-test1
Date: Thu, 24 Jul 2003 18:02:35 +0400 (MSD) [thread overview]
Message-ID: <200307241402.SAA09143@dub.inr.ac.ru> (raw)
In-Reply-To: <20030724000705.4662df54.davem@redhat.com> from "David S. Miller" at éÀÌ 24, 2003 12:07:05
Hello!
> Another idea is to define the user structure:
Actually, I saw it just as array indexed by values from sysctl.h.
Maybe, struct is better, but I am inclined to think in this case it is wrong.
It is going to be extended, so newly compiled applications will see
truncated structs from older kernels and will have to do ugly job
verifying validity of fields using some offsetof. In the case of array
it is natural at least.
Alexey
PS I know right way is not to change the struct. :-)
It is another reason why I am still not sure that encoding
sysctl values as separate subattributes is bad idea.
next prev parent reply other threads:[~2003-07-24 14:02 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
2003-07-24 7:07 ` David S. Miller
2003-07-24 14:02 ` kuznet [this message]
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=200307241402.SAA09143@dub.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=davem@redhat.com \
--cc=krkumar@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.