public inbox for
help / color / mirror / Atom feed
From: Sebastian Huber <>
Subject: [newlib-cygwin] add SIOCGIFDATA ioctl
Date: Mon, 11 Jul 2022 11:52:44 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=9dd91a8330a968aaf970d32dd3a72f1e5dd72b43

commit 9dd91a8330a968aaf970d32dd3a72f1e5dd72b43
Author: Ed Maste <>
Date:   Mon Sep 28 16:54:39 2020 +0000

    add SIOCGIFDATA ioctl
    For interfaces that do not support SIOCGIFMEDIA (for which there are
    quite a few) the only fallback is to query the interface for
    if_data->ifi_link_state.  While it's possible to get at if_data for an
    interface via getifaddrs(3) or sysctl, both are heavy weight mechanisms.
    SIOCGIFDATA is a simple ioctl to retrieve this fast with very little
    resource use in comparison.  This implementation mirrors that of other
    similar ioctls in FreeBSD.
    Submitted by:   Roy Marples <>
    Reviewed by:    markj
    MFC after:      1 month
    Differential Revision:

 newlib/libc/sys/rtems/include/sys/sockio.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/newlib/libc/sys/rtems/include/sys/sockio.h b/newlib/libc/sys/rtems/include/sys/sockio.h
index 447e2c884..03502d770 100644
--- a/newlib/libc/sys/rtems/include/sys/sockio.h
+++ b/newlib/libc/sys/rtems/include/sys/sockio.h
@@ -83,6 +83,7 @@
 #define	SIOCSIFDESCR	 _IOW('i', 41, struct ifreq)	/* set ifnet descr */ 
 #define	SIOCGIFDESCR	_IOWR('i', 42, struct ifreq)	/* get ifnet descr */ 
 #define	SIOCAIFADDR	 _IOW('i', 43, struct ifaliasreq)/* add/chg IF alias */
+#define	SIOCGIFDATA	 _IOW('i', 44, struct ifreq)	/* get if_data */
 #define	SIOCADDMULTI	 _IOW('i', 49, struct ifreq)	/* add m'cast addr */
 #define	SIOCDELMULTI	 _IOW('i', 50, struct ifreq)	/* del m'cast addr */

                 reply	other threads:[~2022-07-11 11:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).