<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=utf-8" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<div style="">

<p dir="auto">Just to be sure, you mean that two threads sending at the same time is not supported, not sending & receiving from 2 different threads.</p>

<p dir="auto">In which case that should work for us, the creation of receiver/sender threads should act as the required memory barrier (since we spawn the threads after the <code>gnutls_handshake</code> call returns); at least as far as the <code>recv_state</code> variable is concerned; but then I'm not sure this would work for <code>initial_negotiation_completed</code> since it would be modified by the thread completing the handshake at a later time right?</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/merge_requests/935#note_144810593">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/sent_notifications/67e2bcd77435f091be1309ad9871a6ea/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/935#note_144810593"}}</script>

</p>

</div>

</body>

</html>