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>
This commit is contained in:
Satheesh Kumar K 2019-11-21 20:33:42 -08:00
parent 1e76492b10
commit 21a93a5f1b
2 changed files with 7 additions and 3 deletions

View File

@ -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);

View File

@ -97,8 +97,14 @@ struct zebra_mlag_info {
/* MLAG Thread context 'master' */
struct thread_master *th_master;
/* Threads for read/write. */
/*
* Event for Initial MLAG Connection setup & Data Read
* Read can be performed only after successful connection establishment,
* so no issues.
*
*/
struct thread *t_read;
/* Event for MLAG write */
struct thread *t_write;
};