diff options
| author | Satheesh Kumar K <sathk@cumulusnetworks.com> | 2019-11-21 20:33:42 -0800 |
|---|---|---|
| committer | Satheesh Kumar K <sathk@cumulusnetworks.com> | 2019-11-21 20:39:35 -0800 |
| commit | 21a93a5f1b8c3ebd1f0c39a8eabd777d0788e384 (patch) | |
| tree | 9316450ab3f1169b34cce7c2ef4d49cfbf8d5379 /zebra/zebra_mlag_private.c | |
| parent | 1e76492b10844df77b64e7954b35f9a8ffc02e74 (diff) | |
zebra: Fixing Comments in MLAG Read scheduling Events
Zebra MLAG is using "t_read" for multiple tasks, such as
1. For opening Communication channel with MLAG
2. In case conncetion fails, same event is used for retries
3. after the connection establishment, same event is used to
read the data from MLAG
since all these taks will never schedule together, this will not
cause any issues.
Signed-off-by: Satheesh Kumar K <sathk@cumulusnetworks.com>
Diffstat (limited to 'zebra/zebra_mlag_private.c')
| -rw-r--r-- | zebra/zebra_mlag_private.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/zebra/zebra_mlag_private.c b/zebra/zebra_mlag_private.c index 6a31d47055..4df7b6dd11 100644 --- a/zebra/zebra_mlag_private.c +++ b/zebra/zebra_mlag_private.c @@ -166,8 +166,6 @@ static int zebra_mlag_connect(struct thread *thread) /* Reset the Timer-running flag */ zrouter.mlag_info.timer_running = false; - /* Reset, sothat Next task can be scheduled */ - zrouter.mlag_info.t_read = NULL; svr.sun_family = AF_UNIX; #define MLAG_SOCK_NAME "/var/run/clag-zebra.socket" strlcpy(svr.sun_path, MLAG_SOCK_NAME, sizeof(MLAG_SOCK_NAME) + 1); |