From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id B5EEF461EE
	for <ffmpegdev@gitmailbox.com>; Tue,  9 May 2023 10:16:12 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D8C9C68BF5E;
	Tue,  9 May 2023 13:16:09 +0300 (EEST)
Received: from btbn.de (btbn.de [136.243.74.85])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 7A10768B20A
 for <ffmpeg-devel@ffmpeg.org>; Tue,  9 May 2023 13:16:03 +0300 (EEST)
Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 06F9B132796
 for <ffmpeg-devel@ffmpeg.org>; Tue,  9 May 2023 12:16:03 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org;
 s=mail; t=1683627363;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:mime-version:mime-version:content-type:content-type:
 content-transfer-encoding:content-transfer-encoding:
 in-reply-to:in-reply-to:references:references;
 bh=wzoyua2vusu1r/CzbV3WSpAmGx5OT2qEU78NxmXX67Y=;
 b=XtG+/8PHgT9DzTkjoT0xDE/bwf0YKbf9YMtjr1XZkQy5uqpQeuHaOV5t+SAZ/qYRLKVxd/
 HEPEpXGscdtLD+BA5sZ3ikL0KPkrHQHz30jwhSEhIFD7wkLEJ24RsJftGhag2nPVeNDFP9
 hUIKzXbk2QaD1RKgvpxNzmjo7Nfv1TEPlLA9BkbFnSa6TnIhfgbKQ+zA6GTUo/4gMzaixA
 nEccIfRW4g8kSBnIHcOrIpi181UYzGTVDxO3Lub/j5A9c3zG9zBqlAFWz704azz6uQERB2
 4v8c7ZEJohK7Pf8g72BbZt/eXU1kD/lQ5rFHEcCb+X55jM8zwteSrjG0czHp5g==
Message-ID: <52930e8a-a0e2-8e5b-d61e-f8e08ecc980a@rothenpieler.org>
Date: Tue, 9 May 2023 12:16:55 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.0
To: ffmpeg-devel@ffmpeg.org
References: <20230509101120.61759-1-rcombs@rcombs.me>
Content-Language: en-US, de-DE
From: Timo Rothenpieler <timo@rothenpieler.org>
In-Reply-To: <20230509101120.61759-1-rcombs@rcombs.me>
Subject: Re: [FFmpeg-devel] [PATCH] Add functions to identify devices in
 more ways
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/52930e8a-a0e2-8e5b-d61e-f8e08ecc980a@rothenpieler.org/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On 09/05/2023 12:11, rcombs wrote:
> - cuDeviceGetUuid_v2, giving distinct IDs for different MIG instances
> - cuDeviceGetLuid, giving a Win32 LUID to match with DXGI and other APIs
> - cuDeviceGetByPCIBusId, retrieving a device that matches a PCI bus ID string
> - cuDeviceGetPCIBusId, giving a PCI bus ID string for a device

Looks good to me. What do you need those for?
Interop with D3D1x/Vulkan?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".