I spent some time cleaning up and documenting all this. There are likely
still some things to fix/improve, but we need some user feedback at some
point. Should start a long release-candidate cycle by doing a 1.3rc1
with the current trunk and fix many remaining things in the next RCs?
The worst tha
Le 12/04/2011 17:31, Samuel Thibault a écrit :
> Brice Goglin, le Tue 12 Apr 2011 14:10:33 +0200, a écrit :
>
>> * pci::00:00.0 or pci:00:00.0 for a given PCI device
>>
> I believe we can make the function number optional too.
>
The device number is useless too (all devices on the s
Brice Goglin, le Tue 12 Apr 2011 15:26:37 +0200, a écrit :
> Le 12/04/2011 15:14, Jeff Squyres a écrit :
> > On Apr 12, 2011, at 8:10 AM, Brice Goglin wrote:
> >> * OS devices by class: something like os:net:2 for the 2nd network
> >> interface (not sure it's useful)
> >>
> > I'm not sure it i
Brice Goglin, le Tue 12 Apr 2011 14:10:33 +0200, a écrit :
> * pci::00:00.0 or pci:00:00.0 for a given PCI device
I believe we can make the function number optional too.
> * pci:::c for the c-th PCI device with vendor ID and device
> ID
:c being optional if there is only on
Le 12/04/2011 15:14, Jeff Squyres a écrit :
> On Apr 12, 2011, at 8:10 AM, Brice Goglin wrote:
>
>> I am looking for a good way to specify PCI and OS devices on the
>> command-line (for hwloc-calc and hwloc-bind).
>>
>> The trunk currently supports:
>> * os:foobar with for OS device named foobar
On Apr 12, 2011, at 8:10 AM, Brice Goglin wrote:
> I am looking for a good way to specify PCI and OS devices on the
> command-line (for hwloc-calc and hwloc-bind).
>
> The trunk currently supports:
> * os:foobar with for OS device named foobar (eth0, mlx4_0, ...)
> * pci::00:00.0 or pci:00:00
