- Original Message -
- Original Message -
Bezüglich Bryan Venteicher's Nachricht vom 27.08.2013 06:18 (localtime):
...
snip
The intr usage is higher than the other drivers you compared against
because if_vmx does the off-level processing in ithreads where as the
Bezüglich Bryan Venteicher's Nachricht vom 27.08.2013 06:18 (localtime):
...
It seems if_vmx doesn't support jumbo frames. If I set mtu 9000, I get
»vmx0: cannot populate Rx queue 0«, I have no problems using jumbo
frames with vmxnet3.
This could fail for two reasons - could not allocate
- Original Message -
Bezüglich Bryan Venteicher's Nachricht vom 27.08.2013 06:18 (localtime):
...
It seems if_vmx doesn't support jumbo frames. If I set mtu 9000, I get
»vmx0: cannot populate Rx queue 0«, I have no problems using jumbo
frames with vmxnet3.
This could fail
- Original Message -
Bezüglich Bryan Venteicher's Nachricht vom 05.08.2013 02:12 (localtime):
Hi,
I've ported the OpenBSD vmxnet3 ethernet driver to FreeBSD. I did a
lot of cleanup, bug fixes, new features, etc (+2000 new lines) along
the way so there is not much of a
Bezüglich Bryan Venteicher's Nachricht vom 05.08.2013 02:12 (localtime):
Hi,
I've ported the OpenBSD vmxnet3 ethernet driver to FreeBSD. I did a
lot of cleanup, bug fixes, new features, etc (+2000 new lines) along
the way so there is not much of a resemblance left.
The driver is in good
On 8/6/13 6:52 AM, Bryan Venteicher wrote:
- Original Message -
I have ~100 FreeBSD 8/9 VMs in my vSphere 5.1 environment, all using the
VMware tools package from VMware. Everything has been running great for
years.
(we skipped vSphere 5.0). Why should I use this vmxnet driver instead
- Original Message -
it'd be nice if we could get vmware to just support the drivers in tree..
by which I mean, just submit patches.. why do they need to have it out
of tree?
I agree. But they are all unfriendly licensed. The FF had a discussion
to get them relicensed to something
- Original Message -
Perhaps not, but they do support FreeBSD. I've started several support cases
with FreeBSD-specific problems and they've fixed all so far.
Yes, it is not a blackhole of support. At $JOB, we got caught by the FreeBSD
specific issue of the busted timer that was
6 aug 2013 kl. 08:05 skrev Bryan Venteicher bry...@daemoninthecloset.org:
- Original Message -
Perhaps not, but they do support FreeBSD. I've started several support cases
with FreeBSD-specific problems and they've fixed all so far.
Yes, it is not a blackhole of support. At
On Sun, Aug 04, 2013 at 07:12:17PM -0500, Bryan Venteicher wrote:
Hi,
I've ported the OpenBSD vmxnet3 ethernet driver to FreeBSD. I did a
lot of cleanup, bug fixes, new features, etc (+2000 new lines) along
the way so there is not much of a resemblance left.
The driver is in good enough
- Original Message -
I have ~100 FreeBSD 8/9 VMs in my vSphere 5.1 environment, all using the
VMware tools package from VMware. Everything has been running great for
years.
(we skipped vSphere 5.0). Why should I use this vmxnet driver instead of the
VMware tools driver or the
On Mon, Aug 05, 2013 at 05:52:01PM -0500, Bryan Venteicher wrote:
- Original Message -
I have ~100 FreeBSD 8/9 VMs in my vSphere 5.1 environment, all using the
VMware tools package from VMware. Everything has been running great for
years.
(we skipped vSphere 5.0). Why should I
12 matches
Mail list logo
