Thanks for the suggestion. We will evaluate the impact for this change.
Best Regards,
Ye Ting
From: Thomas Rognon [mailto:tcrog...@gmail.com]
Sent: Friday, August 22, 2014 1:03 PM
To: edk2-devel
Subject: Re: [edk2] Asynchronous TCP issue
If this is implementation behavior and not spec, maybe
e beginning and release the
> lock at the end.
>
> In your case, would you please describe the “callback finishes” more
> detail? Do you mean the “callback” includes a Tcp4->Transmit() call and you
> need wait for this call finish before entering Tcp4->Receive()?
>
>
>
&
]
Sent: Thursday, August 21, 2014 11:47 AM
To: edk2-devel
Subject: Re: [edk2] Asynchronous TCP issue
By callback, I mean the notify function that is passed into Tcp4->Accept() /
Tcp4->Transmit() / Tcp4->Receive() / etc. I'll say notify function instead of
callback, since that seems to
Receive()?
>
>
>
> Best Regards,
>
> Ye Ting
>
>
>
> *From:* Thomas Rognon [mailto:tcrog...@gmail.com]
> *Sent:* Thursday, August 21, 2014 9:12 AM
> *To:* edk2-devel
> *Subject:* [edk2] Asynchronous TCP issue
>
>
>
> I have a driver that needs to do async
cp4->Transmit() call and you need wait for
this call finish before entering Tcp4->Receive()?
Best Regards,
Ye Ting
From: Thomas Rognon [mailto:tcrog...@gmail.com]
Sent: Thursday, August 21, 2014 9:12 AM
To: edk2-devel
Subject: [edk2] Asynchronous TCP issue
I have a driver that needs to do async T
I have a driver that needs to do async TCP in the background while other
UEFI apps are running. The flow needs to go like this:
{
Tcp4->Accept(); // async
}
AcceptCallback() {
Tcp4->Transmit(); // async
}
TransmitCallback() {
Tcp4->Receive(); // async
}
This works up until Tcp4->Receive()
