Print Initialized Ordered with airSlate SignNow

Print initialized ordered

the final thing we look we look at this the art class and how it is different from the critical block and clinical block now if you look at this if i run this result over here especially for this do loop if you look at it the dough loop executes haffa in a half a sad manner the doula basic gets in a half-ass odd manner from prints out and 12 like this on the other hand what if i want the threats to buy water value want the results to be in an ordered manner and the execution should be in an ordered manner despite it should be bad or the same with the execution should be in you know in ordered man ur okay by preserving the thread daughter okay that's that's what I'm going to do that's that's the use of order so what happens is that lady I suppose if I have a critical block let us say suppose if I have a critical block let's say what critical blob does is that it makes sure the threads behave serially inside a parallel regime okay that's what we saw if you want so if you want to if you want the codes to be executed one thread after the other okay one line after the other with with aft one thread after the other thread some kind of a queue inside a pebble block then you need critical block so the one fundamental the not think the the thing about critical block is that it makes instructions run see you inside parallel regime and it does not preserve the thread order it mean not preserve the third order sometimes it preserves the thread order and you might get the order it might work out in the same order like 120 1 2 3 4 like that some but most of the cases the threat order is not preserved okay in critical block so if I so what I do is that let me activate this oil pee pad will do with last private and then I run these statements in with the critical block okay and now let me run this have a several times if you look at it if you look at it the threads are in a threats are in random order they behaved they are executed one after the other commands are executed one after and everything by the thread where the threats are in random order like one instruction by one stuff and something like that but anyway the thread I mean the thread order is entirely different thread or is entirely different so if I do this again if you do is multiple times usually they go one after the other without without avoiding by avoiding race conditions they use critical block there the race conditions are kind of avoided so it's not of thing now what if i want the thread order to be maintained during this process and that's where the order class go sent for that what i need to do is as follows i need to include this class called as ordered over here and to make sure that the odd orders work i have to write this directive colors OMP order and this got it that what this does is that it executes the statement just like the critical block but it maintains the thread order so now let me clear this up clear this up and i run this you look at it the thread order is proper immaculate immaculately proper no matter how many times i run the thread order is the same on the other hand if i had to have had to remove if i were to remove the thread order and write critical critical you just to give you guys an idea what's happening if at all do this again see the thread order is jumbled up although they execute statements execute one thread after the other this is statements are jumbled up Satan's are jumbled up and because the threads are being jumbled okay now here's the thing here's the thing suppose suppose I run this statement I run this statement I will be parallel to last private without the order without the ordered keyword let's say without the order keyboard let's say and with all the ordered keyword with an order keyword let's say one might anticipate that this block will behave in an orderly manner okay the fact is it doesn't it will throw an error it says it or it says it it says an ordered region must be closely nested inside a loop inside a loop region with an ordered class what it means is that if suppose if you want to use this ordered class I mean if you want to use the order directive then there should be a pal regime battles panel region with ordered class on the top so if i remove the ordered class and if you just want to use the ordered a directive it won't work so if i write this order class ordered keyword again i mean the class again and then it run it it works fine okay so that's one thing on the other hand critical block as you guys know as you guys must have noticed okay critical block is independent ordered the order means the vertical directive is independent and as the order directive means the order class to be working fine so those are the summaries be noticed critical block make sure makes the instructions not see really inside a parallel regime need not preserve the thread order whereas order class order okay ordered block ordered block makes instructions run serial inside a panel dojin preserves the thread order executed by having a thread order director by not a director and an finally needs and order class or applause okay executed by having an order directive okay and this one II this one executed by having a critical directive okay okay now with that this prob with that this Expo this tutorial is over and this tutorial is over and we discussed about the private class first period class last private class critical block and hard block in quite quite quite details I next few to next tutorials will be considering on summer classes and some are interesting console that be that are available in openmp okay thank you can to them thank you guys for watching and I'll see you guys next time