> -----Original Message-----
> From: Flavio Leitner <[email protected]>
> Sent: Thursday, February 14, 2019 2:56 PM
> To: Ilya Maximets <[email protected]>
> Cc: Ian Stokes <[email protected]>; Ophir Munk
> <[email protected]>; [email protected]; Thomas Monjalon
> <[email protected]>
> Subject: Re: [ovs-dev] [PATCH v1] doc: Add "Representors" topic document
>
> On Thu, Feb 14, 2019 at 01:47:27PM +0300, Ilya Maximets wrote:
> > On 13.02.2019 19:39, Ian Stokes wrote:
> > > On 2/13/2019 8:14 AM, Ophir Munk wrote:
> > >>
> >
> > Anyway, The instructions for most of NICs, I guess, should be "just
> > echo number of VFs to 'max_vfs' sysfs knob". We may add this
> > information right here and make a remark that some NICs may require
> > additional steps. We may also point to the openstack ovs-offload
> > guide, first parts of it describes how to configure representors with
> Mellanox NICs.
> > IMHO, this amount of information should be enough and it does not
> > deserve a separate manual.
>
> I agree it would be very useful to have instructions on how to put the card in
> the correct state to use the representors. However, I'd avoid pointing to
> other guides outside of OVS because we don't control them, so they can
> change and move and our side will break. Also that usually they include more
> instruction/details than actually is needed to make it work, which can be
> confusing.
>
> I think people building OSP, for instance (but could be any other project),
> would look after OVS documentation on how to build their side and not vice-
> versa :-).
>
> fbl
>
I can drop the link to the external documents.
The openstack document for example refers to ovs-kernel which may be confused
with ovs-dpdk.
To avoid confusion I will add all the information inside the OVS document here.
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
