2013-10-03 23:42:26 -05:00
|
|
|
/* -*- Mode: C; tab-width: 4; indent-tabs-mode: t; c-basic-offset: 4 -*- */
|
|
|
|
|
/* NetworkManager -- Network link manager
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
|
* (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU General Public License along
|
|
|
|
|
* with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
|
* 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2013 Red Hat, Inc.
|
|
|
|
|
*/
|
|
|
|
|
|
all: fix up multiple-include-guard defines
Previously, src/nm-ip4-config.h, libnm/nm-ip4-config.h, and
libnm-glib/nm-ip4-config.h all used "NM_IP4_CONFIG_H" as an include
guard, which meant that nm-test-utils.h could not tell which of them
was being included (and so, eg, if you tried to include
nm-ip4-config.h in a libnm test, it would fail to compile because
nm-test-utils.h was referring to symbols in src/nm-ip4-config.h).
Fix this by changing the include guards in the non-API-stable parts of
the tree:
- libnm-glib/nm-ip4-config.h remains NM_IP4_CONFIG_H
- libnm/nm-ip4-config.h now uses __NM_IP4_CONFIG_H__
- src/nm-ip4-config.h now uses __NETWORKMANAGER_IP4_CONFIG_H__
And likewise for all other headers.
The two non-"nm"-prefixed headers, libnm/NetworkManager.h and
src/NetworkManagerUtils.h are now __NETWORKMANAGER_H__ and
__NETWORKMANAGER_UTILS_H__ respectively, which, while not entirely
consistent with the general scheme, do still mostly make sense in
isolation.
2014-08-13 14:10:11 -04:00
|
|
|
#ifndef __NETWORKMANAGER_DCB_H__
|
|
|
|
|
#define __NETWORKMANAGER_DCB_H__
|
2013-10-03 23:42:26 -05:00
|
|
|
|
2015-07-17 14:38:54 +02:00
|
|
|
#include "nm-default.h"
|
2013-10-03 23:42:26 -05:00
|
|
|
#include "nm-setting-dcb.h"
|
|
|
|
|
|
dcb: separate DCB enable/disable and wait for carrier changes (rh #799241) (rh #1081991)
Non-git-master versions of lldpad refuse to touch a device that doesn't
have a carrier. And when enabling/disabling DCB, the kernel driver will
reconfigure itself and may turn carrier off for a few seconds. So we
must ensure that before enabling/disabling DCB, the carrier is already
on. Next we must ensure that *after* enabling/disabling DCB, the
carrier is back on before doing further DCB setup.
There's a race condition between enabling/disabling DCB and receiving
the carrier event in NetworkManager that has to be handled carefully.
Because the carrier may not yet be down after the dcbtool call to
enable/disable DCB returns, we need to wait for a couple seconds for
the carrier to go down, and then again for it to come back up.
Otherwise we might see the still-on carrier, proceed with DCB setup,
and the carrier finally goes down halfway through the setup, which
will fail the operations with "DCB not enabled, link down, or DCB
not supported" errors from lldpad.
2014-03-27 13:49:50 -05:00
|
|
|
gboolean nm_dcb_enable (const char *iface, gboolean enable, GError **error);
|
2013-10-03 23:42:26 -05:00
|
|
|
gboolean nm_dcb_setup (const char *iface, NMSettingDcb *s_dcb, GError **error);
|
|
|
|
|
gboolean nm_dcb_cleanup (const char *iface, GError **error);
|
|
|
|
|
|
|
|
|
|
/* For testcases only! */
|
|
|
|
|
typedef gboolean (*DcbFunc) (char **argv,
|
|
|
|
|
guint which,
|
|
|
|
|
gpointer user_data,
|
|
|
|
|
GError **error);
|
|
|
|
|
|
|
|
|
|
#define DCBTOOL 0
|
|
|
|
|
#define FCOEADM 1
|
|
|
|
|
|
|
|
|
|
gboolean do_helper (const char *iface,
|
|
|
|
|
guint which,
|
|
|
|
|
DcbFunc run_func,
|
|
|
|
|
gpointer user_data,
|
|
|
|
|
GError **error,
|
|
|
|
|
const char *fmt,
|
|
|
|
|
...) G_GNUC_PRINTF(6, 7);
|
|
|
|
|
|
dcb: separate DCB enable/disable and wait for carrier changes (rh #799241) (rh #1081991)
Non-git-master versions of lldpad refuse to touch a device that doesn't
have a carrier. And when enabling/disabling DCB, the kernel driver will
reconfigure itself and may turn carrier off for a few seconds. So we
must ensure that before enabling/disabling DCB, the carrier is already
on. Next we must ensure that *after* enabling/disabling DCB, the
carrier is back on before doing further DCB setup.
There's a race condition between enabling/disabling DCB and receiving
the carrier event in NetworkManager that has to be handled carefully.
Because the carrier may not yet be down after the dcbtool call to
enable/disable DCB returns, we need to wait for a couple seconds for
the carrier to go down, and then again for it to come back up.
Otherwise we might see the still-on carrier, proceed with DCB setup,
and the carrier finally goes down halfway through the setup, which
will fail the operations with "DCB not enabled, link down, or DCB
not supported" errors from lldpad.
2014-03-27 13:49:50 -05:00
|
|
|
gboolean _dcb_enable (const char *iface,
|
|
|
|
|
gboolean enable,
|
|
|
|
|
DcbFunc run_func,
|
|
|
|
|
gpointer user_data,
|
|
|
|
|
GError **error);
|
|
|
|
|
|
2013-10-03 23:42:26 -05:00
|
|
|
gboolean _dcb_setup (const char *iface,
|
|
|
|
|
NMSettingDcb *s_dcb,
|
|
|
|
|
DcbFunc run_func,
|
|
|
|
|
gpointer user_data,
|
|
|
|
|
GError **error);
|
|
|
|
|
|
|
|
|
|
gboolean _dcb_cleanup (const char *iface,
|
|
|
|
|
DcbFunc run_func,
|
|
|
|
|
gpointer user_data,
|
|
|
|
|
GError **error);
|
|
|
|
|
|
|
|
|
|
gboolean _fcoe_setup (const char *iface,
|
|
|
|
|
NMSettingDcb *s_dcb,
|
|
|
|
|
DcbFunc run_func,
|
|
|
|
|
gpointer user_data,
|
|
|
|
|
GError **error);
|
|
|
|
|
|
|
|
|
|
gboolean _fcoe_cleanup (const char *iface,
|
|
|
|
|
DcbFunc run_func,
|
|
|
|
|
gpointer user_data,
|
|
|
|
|
GError **error);
|
|
|
|
|
|
all: fix up multiple-include-guard defines
Previously, src/nm-ip4-config.h, libnm/nm-ip4-config.h, and
libnm-glib/nm-ip4-config.h all used "NM_IP4_CONFIG_H" as an include
guard, which meant that nm-test-utils.h could not tell which of them
was being included (and so, eg, if you tried to include
nm-ip4-config.h in a libnm test, it would fail to compile because
nm-test-utils.h was referring to symbols in src/nm-ip4-config.h).
Fix this by changing the include guards in the non-API-stable parts of
the tree:
- libnm-glib/nm-ip4-config.h remains NM_IP4_CONFIG_H
- libnm/nm-ip4-config.h now uses __NM_IP4_CONFIG_H__
- src/nm-ip4-config.h now uses __NETWORKMANAGER_IP4_CONFIG_H__
And likewise for all other headers.
The two non-"nm"-prefixed headers, libnm/NetworkManager.h and
src/NetworkManagerUtils.h are now __NETWORKMANAGER_H__ and
__NETWORKMANAGER_UTILS_H__ respectively, which, while not entirely
consistent with the general scheme, do still mostly make sense in
isolation.
2014-08-13 14:10:11 -04:00
|
|
|
#endif /* __NETWORKMANAGER_DCB_H__ */
|