>The guest-facing side of the VSWITCH does not support LACP. >(Let's avoid terms like "port side" and "trunk side". When a guest is >using a virtual trunk, which side is the "trunk side"?) LACP is the thing >that lets the host and switch coordinate traffic.
Ok, that's a better terminology, guest-facing and host-facing side. I got my wording from our Cisco people, but they live in a different world :-) >The only use of LACP that I've seen/heard about so far is for better error >toleration and recovery, better physical OSA management (dynamically >delete from group so you can put on microcode fixes, then re-add), Yes, a really usefull capability. That's why I moved all my GbEs to VSWITCH. I really wouldn't like to take some out again. >While you can have multiple vNICs on an aggregating VSWITCH, there's >nothing that will spray/deal queued frames across the vNICs since they each have a unique MAC address. Alan, can you comment on what may have happened to the test Mark ran with bonding mode 2? Would it really behave like bonding mode 1? It sounded like it worked (well, gave no errors in setting up), but do you expect it to accomplish something usefull? >But even if it did, you're doomed if the >buffer fill rate is higher than the consumption rate. All you've done is >delay slightly the point at which all guest buffers are full. Of course you can't fill more than you consume. But with more buffers you can consume in larger batches, then turn to other work or fall asleep. This will make you more Q3 instead of Q1, which is more efficient for large transfers. Best regards, Pieter Harder pieter.har...@brabantwater.nl tel +31-73-6837133 / +31-6-47272537 Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
