[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB3763A67B9AEFC48BAAFA9C5AB02FA@BY5PR12MB3763.namprd12.prod.outlook.com>
Date: Wed, 5 Jul 2023 18:37:42 +0000
From: Ankit Agrawal <ankita@...dia.com>
To: Alex Williamson <alex.williamson@...hat.com>
CC: Jason Gunthorpe <jgg@...dia.com>,
Aniket Agashe <aniketa@...dia.com>, Neo Jia <cjia@...dia.com>,
Kirti Wankhede <kwankhede@...dia.com>,
"Tarun Gupta (SW-GPU)" <targupta@...dia.com>,
Vikram Sethi <vsethi@...dia.com>,
Andy Currid <ACurrid@...dia.com>,
Alistair Popple <apopple@...dia.com>,
John Hubbard <jhubbard@...dia.com>,
Dan Williams <danw@...dia.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v4 1/1] vfio/nvgpu: Add vfio pci variant module for grace
hopper
> I had also asked in the previous review whether "nvgpu" is already overused. I
> see a python tool named nvgpu, an OpenXLA tool, various nvgpu things related
> to Tegra, an nvgpu dialect for MLIR, etc. There are over 5,000 hits on google for
> "nvgpu", only a few of which reference development of this module. Is there a
> more unique name we can use? Thanks,
Sorry, had missed this comment. Are you suggesting changing the module name
or just reduce the number of times we use the nvgpu keyword in all the functions
of the module? I don't see any in-tree or vfio-pci module with a similar *nvgpu*
name, and the clash appears to be with items outside of the kernel tree. Given
that, should we still change the module name as nvgpu-vfio-pci sounds a relevant
name here? Thanks.
Powered by blists - more mailing lists