Lines Matching refs:grace

930 	grace periods obey the rules of RCU, in particular, the
1517 rests on two concepts: grace periods and read-side critical sections.
1519 A grace period is the span of time occupied by a call to
1527 span a full grace period.  In more detail, the Guarantee says:
1529 	For any critical section C and any grace period G, at least
1541 before and end after a grace period.
1568 P1's grace period, contrary to part (2) of the Guarantee.  On the
1571 the grace period, contrary to part (1).  Together the results violate
1577 starts before a grace period does then the critical section's CPU will
1579 some time before the grace period's synchronize_rcu() call returns.
1580 And if a critical section ends after a grace period does then the
1586 before" or "ends after" a grace period?  Some aspects of the meaning
1603 grace periods and read-side critical sections into the picture, in the
1607 	and that event is a synchronize_rcu() fence (i.e., a grace
1618 grace period which ends before Z begins.  (In fact it covers more than
1653 This formula means that G and W are the same event (a grace period),
1666 From 1 - 4 we deduce that the grace period G ends before the critical
1712 violated: A critical section starts before a grace period, and some
1715 the end of the grace period.
1719 question, and let S be the synchronize_rcu() fence event for the grace
1723 relation, and R is po-before the grace period S.  Thus we have:
1742 Since S is a grace period we have S ->rcu-gp S, and since L and U are
1778 because S is a grace period.
1848 section in P0 both starts before P1's grace period does and ends
1850 grace period does and ends after it does.
1854 relations srcu-gp and srcu-rscsi added to represent SRCU grace periods
1871 	same domain.  Read-side critical sections and grace periods
1874 	to pairs of critical sections and grace periods having the
2540 really do anything, because there aren't any grace periods.  They are
2605 before the grace period in P0 does, because RCU's Grace-Period