From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: dhan lin <dhan.lin1989@gmail.com>, netdev@vger.kernel.org
Subject: Re: Need more information on "ifi_change" in "struct ifinfomsg"
Date: Fri, 6 Sep 2019 16:55:59 +0200 [thread overview]
Message-ID: <16579c2d-d0b7-179f-5381-3803118a8972@6wind.com> (raw)
In-Reply-To: <CAMvS6vbeo5tBADNmLvkXUuSSHmxVpt3UW+jZtxY2Le9nXRbNDw@mail.gmail.com>
Le 06/09/2019 à 07:08, dhan lin a écrit :
> Hi All,
>
> There is a field called ifi_change in "struct ifinfomsg". man page for
> rtnetlink says its for future use and should be always set to
> 0xFFFFFFFF.
>
> But ive run some sample tests, to confirm the value is not as per man
> pages explanation.
> Its 0 most of the times and non-zero sometimes.
>
> I've the following question,
>
> Is ifi_change set only when there is a state change in interface values?
ifi_change indicates which flags (ifi_flags) have changed.
It does not cover other changes.
Regards,
Nicolas
next prev parent reply other threads:[~2019-09-06 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMvS6vYbphKKM4evbV6Vre7vaR8r+oJgZ8TuQU6VtBSjVqH7dA@mail.gmail.com>
2019-09-06 5:08 ` Need more information on "ifi_change" in "struct ifinfomsg" dhan lin
2019-09-06 14:55 ` Nicolas Dichtel [this message]
2019-09-06 16:39 ` dhan lin
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=16579c2d-d0b7-179f-5381-3803118a8972@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=dhan.lin1989@gmail.com \
--cc=netdev@vger.kernel.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