On Wed, Nov 05, 2014 at 09:57:25PM -0200, Flavio Leitner wrote: > On Wed, Nov 05, 2014 at 03:51:30PM -0800, Andy Zhou wrote: > > On Wed, Nov 5, 2014 at 3:47 PM, Flavio Leitner <f...@redhat.com> wrote: > > > On Wed, Nov 05, 2014 at 03:23:24PM -0800, Andy Zhou wrote: > > >> On Wed, Nov 5, 2014 at 2:56 PM, Flavio Leitner <f...@redhat.com> wrote: > > >> > On Wed, Nov 05, 2014 at 02:07:08PM -0800, Ben Pfaff wrote: > > >> >> On Wed, Nov 05, 2014 at 08:04:29PM -0200, Flavio Leitner wrote: > > >> >> > The above is not available in Fedora 20. > > >> >> > # stat /sys/module/openvswitch/version > > >> >> > stat: cannot stat ???/sys/module/openvswitch/version???: No such > > >> >> > file or > > >> >> > directory > > >> >> > # uname -r > > >> >> > 3.16.7-200.fc20.x86_64 > > >> >> > > >> >> You only get it with the out-of-tree module (which is expected). > > >> > > > >> > Right, though I think the in-tree module could export the version > > >> > as well, so that we could track that too. For example: > > >> > > > >> > $ modinfo openvswitch | grep vermagic > > >> > vermagic: 3.16.7-200.fc20.x86_64... > > >> Will this always be the same as the OS version? I think the > > >> controller / user space may be more interested in OVS version, > > > > > > Define OVS version, because to me that is the OVS datapath version. > > > > The version number assigned to each OVS release. > > http://openvswitch.org/releases/ > > out-of-tree kernel module is part of a release. > > Sorry, I meant for the in-tree kernel module.
I guess we could report the Linux kernel version if the module itself doesn't already have a version, would that help? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
