Hi Xavi/Diego,

 

Can’t we use the RC_BUSY rather than CT_ERROR  for the case of Concurrent 
transactions.  

 

The scheduling function may decide for a retry when a RC_BUSY is received , so 
how we can differentiate the usage of CT_ERROR and RC_BUSY.

 

Is it the backoff time that accounts.  

 

Thanks & Regards,

Lijo Thomas 

 

 

From: 6tisch [mailto:[email protected]] On Behalf Of Xavier Vilajosana
Sent: 14 May 2016 18:34
To: Prof. Diego Dujovne
Cc: [email protected]
Subject: Re: [6tisch] New error type for concurrent transactions on 6top 
protocol draft

 

Hi Diego,

 

What I propose is to lock in the schedule the cells that are being sent in the 
candidate list, this means that 1) if there are other cells available in the 
schedule, the node may still be able to propose another (non-overlapping) 
candidate list. thus still supporting concurrency and 2) only in the case that 
the remaining free cells are those in the candidate list, the error code you 
propose will be used to enable a retry.

 

hope this is clear now!

X

 

2016-05-13 16:47 GMT+02:00 Prof. Diego Dujovne <[email protected] 
<mailto:[email protected]> >:

Dear all,

           I proposed today to add a new type of error 

for CellList proposal during the transaction. The idea

follows the solution proposed today at the Webex call
by Xavi to define a lock when two concurrent cell 
requests arrive to the node.

For example, if node B requests a cell from A, 
and during this transaction node C requests a new 
cell from A, send a  Concurrent Transaction "CT_ERROR"

so C knows there may still be resources available and

retry later instead of giving up.

 

Do you think this should solve the problem?


Regards,

                              Diego





-- 

DIEGO DUJOVNE
Académico Escuela de Ingeniería en Informática y Telecomunicaciones
Facultad de Ingeniería UDP
www.ingenieria.udp.cl <http://www.ingenieria.udp..cl> 
(56 2) 676 8125


_______________________________________________
6tisch mailing list
[email protected] <mailto:[email protected]> 
https://www.ietf.org/mailman/listinfo/6tisch

 


-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------

_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch

Reply via email to