9e5d8bd3d1
Previously, `olDestroyQueue` would not actually destroy the queue, instead leaving it for the device to clean up when it was destroyed. Now, the queue is either released immediately if it is complete or put into a list of "pending" queues if it is not. Whenever we create a new queue, we check this list to see if any are now completed. If there are any we release their resources and use them instead of pulling from the pool. This prevents long running programs that create and drop many queues without syncing them from leaking memory all over the place.
33 lines
1011 B
C++
33 lines
1011 B
C++
//===------- Offload API tests - olDestroyQueue ---------------------------===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "../common/Fixtures.hpp"
|
|
#include <OffloadAPI.h>
|
|
#include <gtest/gtest.h>
|
|
|
|
using olDestroyQueueTest = OffloadQueueTest;
|
|
OFFLOAD_TESTS_INSTANTIATE_DEVICE_FIXTURE(olDestroyQueueTest);
|
|
|
|
TEST_P(olDestroyQueueTest, Success) {
|
|
ASSERT_SUCCESS(olDestroyQueue(Queue));
|
|
Queue = nullptr;
|
|
}
|
|
|
|
TEST_P(olDestroyQueueTest, SuccessDelayedResolution) {
|
|
ManuallyTriggeredTask Manual;
|
|
ASSERT_SUCCESS(Manual.enqueue(Queue));
|
|
ASSERT_SUCCESS(olDestroyQueue(Queue));
|
|
Queue = nullptr;
|
|
|
|
ASSERT_SUCCESS(Manual.trigger());
|
|
}
|
|
|
|
TEST_P(olDestroyQueueTest, InvalidNullHandle) {
|
|
ASSERT_ERROR(OL_ERRC_INVALID_NULL_HANDLE, olDestroyQueue(nullptr));
|
|
}
|