delta/openvswitch.git/lib/netdev-patch.c, branch lts-1.0 github.com: openvswitch/ovs.git netdev: Fix carrier status for down interfaces. 2010-11-16T23:17:38+00:00 Jesse Gross jesse@nicira.com 2010-10-27T22:29:16+00:00 efa3112b7c340203decf0061e7d1d12be03a150f Currently netdev_get_carrier() returns both a carrier status and an error code. However, usage of the error code was inconsistent: most callers either ignored it or didn't perform their task if an error occured, which prevented bond rebalancing. This makes the handling consistent by translating an error into a down status in the netdev library. Bug #3959 
Currently netdev_get_carrier() returns both a carrier status and
an error code.  However, usage of the error code was inconsistent:
most callers either ignored it or didn't perform their task if an
error occured, which prevented bond rebalancing.  This makes the
handling consistent by translating an error into a down status in
the netdev library.

Bug #3959
vlog: Introduce VLOG_DEFINE_THIS_MODULE for declaring vlog module in use. 2010-07-21T22:47:09+00:00 Ben Pfaff blp@nicira.com 2010-07-16T18:02:49+00:00 5136ce492c414f377f7be9ae32b259abb9f76580 Adding a macro to define the vlog module in use adds a level of indirection, which makes it easier to change how the vlog module must be defined. A followup commit needs to do that, so getting these widespread changes out of the way first should make that commit easier to review. 
Adding a macro to define the vlog module in use adds a level of
indirection, which makes it easier to change how the vlog module must be
defined.  A followup commit needs to do that, so getting these widespread
changes out of the way first should make that commit easier to review.
vport: Use EBUSY to represent already attached device. 2010-07-15T22:09:08+00:00 Jesse Gross jesse@nicira.com 2010-07-15T02:02:10+00:00 10d3515aa4fc0d338df28d2760fae264c0cea40a We currently use EEXIST to represent both a device that is already attached and for GRE devices that are the same as another one. Instead use EBUSY for already attached devices to disambiguate the two situations. 
We currently use EEXIST to represent both a device that is already
attached and for GRE devices that are the same as another one.
Instead use EBUSY for already attached devices to disambiguate the
two situations.
Implement QoS framework. 2010-06-17T22:04:12+00:00 Ben Pfaff blp@nicira.com 2010-06-17T22:04:12+00:00 c1c9c9c4b636ab2acf2f75024c282a9a497ca9a9 ovs-vswitchd doesn't declare its QoS capabilities in the database yet, so the controller has to know what they are. We can add that later. The linux-htb QoS class has been tested to the extent that I can see that it sets up the queues I expect when I run "tc qdisc show" and "tc class show". I haven't tested that the effects on flows are what we expect them to be. I am sure that there will be problems in that area that we will have to fix. 
ovs-vswitchd doesn't declare its QoS capabilities in the database yet,
so the controller has to know what they are.  We can add that later.

The linux-htb QoS class has been tested to the extent that I can see that
it sets up the queues I expect when I run "tc qdisc show" and "tc class
show".  I haven't tested that the effects on flows are what we expect them
to be.  I am sure that there will be problems in that area that we will
have to fix.
netdev-vport: Use vport set_stats instead of internal dev. 2010-06-10T21:30:51+00:00 Jesse Gross jesse@nicira.com 2010-06-09T19:54:34+00:00 f4b6076acab233cfe02e7eaefdeafbb69dfae556 In certain cases we require the ability to provide stats that are added to the values collected by the kernel (currently only used by bond fake devices). Internal devices previously implemented this directly but now that their stats are now handled by the vport layer the functionality has been moved there. This removes the userspace code to set the stats and replaces it with a mechanism to access the equivalent functionality in the vport layer. 
In certain cases we require the ability to provide stats that are
added to the values collected by the kernel (currently only used
by bond fake devices).  Internal devices previously implemented
this directly but now that their stats are now handled by the vport
layer the functionality has been moved there.  This removes the
userspace code to set the stats and replaces it with a mechanism
to access the equivalent functionality in the vport layer.
patch: Remove veth driver. 2010-05-18T19:57:25+00:00 Jesse Gross jesse@nicira.com 2010-05-14T20:54:16+00:00 2158888d8d8f3b4c00dcf979390a19fa7fcf7942 Now that we have a new patch implementation, remove the veth driver and its userspace components. Then rename 'patchnew' to 'patch'. The new implementation is a drop-in replacement for the old one. 
Now that we have a new patch implementation, remove the veth driver
and its userspace components.  Then rename 'patchnew' to 'patch'.
The new implementation is a drop-in replacement for the old one.
netdev: Add 'patch' userspace implementation. 2010-05-18T19:57:25+00:00 Jesse Gross jesse@nicira.com 2010-05-14T20:49:43+00:00 43694e2a8d950f62781ec6dc613b5dac32de35fd Add a netdev to talk to the 'patch' vport in the kenerl. Since there is currently a 'patch' implementation using the veth driver, this one is temporarily called 'patchnew'. 
Add a netdev to talk to the 'patch' vport in the kenerl.  Since
there is currently a 'patch' implementation using the veth driver,
this one is temporarily called 'patchnew'.