public inbox for
help / color / mirror / Atom feed
From: Sebastian Huber <>
Subject: [newlib-cygwin] Although most of the NIC drivers are epoch ready,
Date: Mon, 11 Jul 2022 11:51:28 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=f3303cf1d5c9fe8236a576fc994052bc7718759a

commit f3303cf1d5c9fe8236a576fc994052bc7718759a
Author: Gleb Smirnoff <>
Date:   Mon Feb 24 21:07:30 2020 +0000

    Although most of the NIC drivers are epoch ready,
    due to peer pressure switch over to opt-in instead of opt-out for epoch.
    Instead of IFF_NEEDSEPOCH, provide IFF_KNOWSEPOCH. If driver marks
    itself with IFF_KNOWSEPOCH, then ether_input() would not enter epoch
    when processing its packets.
    Now this will create recursive entrance in epoch in >90% network
    drivers, but will guarantee safeness of the transition.
    Mark several tested drivers as IFF_KNOWSEPOCH.
    Reviewed by:            hselasky, jeff, bz, gallatin
    Differential Revision:

 newlib/libc/sys/rtems/include/net/if.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/newlib/libc/sys/rtems/include/net/if.h b/newlib/libc/sys/rtems/include/net/if.h
index 2c1ecdf32..78b1654dc 100644
--- a/newlib/libc/sys/rtems/include/net/if.h
+++ b/newlib/libc/sys/rtems/include/net/if.h
@@ -144,7 +144,7 @@ struct if_data {
 #define	IFF_DEBUG	0x4		/* (n) turn on debugging */
 #define	IFF_LOOPBACK	0x8		/* (i) is a loopback net */
 #define	IFF_POINTOPOINT	0x10		/* (i) is a point-to-point link */
-#define	IFF_NEEDSEPOCH	0x20		/* (i) calls if_input w/o epoch */
+#define	IFF_KNOWSEPOCH	0x20		/* (i) calls if_input in net epoch */
 #define	IFF_DRV_RUNNING	0x40		/* (d) resources allocated */
 #define	IFF_NOARP	0x80		/* (n) no address resolution protocol */
 #define	IFF_PROMISC	0x100		/* (n) receive all packets */
@@ -178,7 +178,7 @@ struct if_data {
  * Values for if_link_state.

                 reply	other threads:[~2022-07-11 11:51 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).