On Mon, Jul 22, 2013 at 09:10:52AM -0700, Alex Wang wrote:
> Looks good to me,
>
> Want to ask question about "ovsthread_once_start()",
> 1. why do we have "ovsthread_once_start()" defined in header file?
The "fast path" for using ovsthread_once_start() is just a test and
conditional jump. The a
Oh! How could I not see the "inline". Sorry for the nonsense,
On Mon, Jul 22, 2013 at 10:39 AM, Ben Pfaff wrote:
> On Mon, Jul 22, 2013 at 10:35:27AM -0700, Alex Wang wrote:
> > On Mon, Jul 22, 2013 at 10:23 AM, Ben Pfaff wrote:
> >
> > > On Mon, Jul 22, 2013 at 09:10:52AM -0700, Alex Wang wro
On Mon, Jul 22, 2013 at 10:35:27AM -0700, Alex Wang wrote:
> On Mon, Jul 22, 2013 at 10:23 AM, Ben Pfaff wrote:
>
> > On Mon, Jul 22, 2013 at 09:10:52AM -0700, Alex Wang wrote:
> > > Looks good to me,
> > >
> > > Want to ask question about "ovsthread_once_start()",
> > > 1. why do we have "ovsthr
Thanks Ben for the explanation,
On Mon, Jul 22, 2013 at 10:23 AM, Ben Pfaff wrote:
> On Mon, Jul 22, 2013 at 09:10:52AM -0700, Alex Wang wrote:
> > Looks good to me,
> >
> > Want to ask question about "ovsthread_once_start()",
> > 1. why do we have "ovsthread_once_start()" defined in header fil
Looks good to me,
Want to ask question about "ovsthread_once_start()",
1. why do we have "ovsthread_once_start()" defined in header file?
2. if __check__ is defined, the macro function will override the
previously defined "ovsthread_once_start()" function. Right?
3. could you explain why you use
