Re: FreeBSD Port: emulators/virtio-kmod - poor performance in VirtualBox
Hi, - Original Message - > From: "Marek Salwerowicz" > To: kuriy...@freebsd.org > Cc: po...@freebsd.org, emulat...@freebsd.org > Sent: Sunday, November 25, 2012 6:55:33 PM > Subject: FreeBSD Port: emulators/virtio-kmod - poor performance in VirtualBox > > Hi, > > I would like to test the 'intnet' networking mode in VirtualBox 4.2.4 > (under FreeBSD 9.1-PRERELEASE), running 2 VMs with FreeBSD 9.1-RC3 > amd64 > each. > > After installing your port kernel detected the 'virtio' interface and > I > configured the IP on both machines. > > I used the 'ttcp' program to test the network performance between > machines and I noticed that average transfer rate is around 6-7 KB/s > (while using eg. the Intel emulator, |82540EM, it's much better, > around > 100 KB/s) Even 100KB seems a couple of magnitudes slow for the emulated E1000 between 2 guests on the same host. > > Do you have an idea why this is so slow? > Try disabling checksum offloading (and TSO/LRO if Virtualbox supports that). > And why the if_vtnet network driver isn't provided in GENERIC kernel? > Is it still under development? > Getting it in GENERIC is in my plans. My spare time has been distracted at some other Ethernet drivers for the last few weeks. I hope to spend much of my spare time in Dec. on various VirtIO items. Bryan > Regards, > > -- > Marek Salwerowicz > | > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: emulators/virtio-kmod - poor performance in VirtualBox
W dniu 2012-11-26 01:55, Marek Salwerowicz pisze: Hi, I would like to test the 'intnet' networking mode in VirtualBox 4.2.4 (under FreeBSD 9.1-PRERELEASE), running 2 VMs with FreeBSD 9.1-RC3 amd64 each. and 'virtio' NIC type, of course... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: emulators/virtio-kmod - poor performance in VirtualBox
Hi, I would like to test the 'intnet' networking mode in VirtualBox 4.2.4 (under FreeBSD 9.1-PRERELEASE), running 2 VMs with FreeBSD 9.1-RC3 amd64 each. After installing your port kernel detected the 'virtio' interface and I configured the IP on both machines. I used the 'ttcp' program to test the network performance between machines and I noticed that average transfer rate is around 6-7 KB/s (while using eg. the Intel emulator, |82540EM, it's much better, around 100 KB/s) Do you have an idea why this is so slow? And why the if_vtnet network driver isn't provided in GENERIC kernel? Is it still under development? Regards, -- Marek Salwerowicz | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "postfix-current" broken on amd64 platform
Peter Jeremy: > I've just bumped into this exact situation with mail/postfix28 and > suspect that earlier postfix ports have the same issue. The above fix > works on postfix28 and I would request that it be added to that port's > patch list. Since this is a workaround for a FreeBSD-specific issue, > I don't believe it's reasonable to expect Wietse to patch old postfix > variants to work around it. Indeed. I rewrote this module for Postfix 2.9. If it deals with this problem, then I won't take further action. Wietse ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "postfix-current" broken on amd64 platform
Resurrecting an old thread because I've just run into this problem...
[postfix dies with a "Protocol not supported" when built in a jail
without an IPv6 address]
On 2011-Nov-17 15:41:12 -0500, Wietse Venema wrote:
>A more proactive workaround would be to treat "protocol not supported"
>as a non-fatal error, just like "address family not supported" is.
>
>Please let me know if this works in the build cluster. It will log
>a warning but that should be justfied, because the system does have
>an abnormal configuration.
>
> Wietse
>
>*** src/util/inet_proto.c- Tue Jan 8 15:36:13 2008
>--- src/util/inet_proto.c Thu Nov 17 08:49:31 2011
>***
>*** 219,225
> pf->dns_atype_list = make_unsigned_vector(3, T_A, T_, 0);
> pf->sa_family_list = make_uchar_vector(3, AF_INET, AF_INET6, 0);
> break;
>! } else if (errno == EAFNOSUPPORT) {
> msg_warn("%s: IPv6 support is disabled: %m", context);
> msg_warn("%s: configuring for IPv4 support only", context);
> /* FALLTHROUGH */
>--- 219,225
> pf->dns_atype_list = make_unsigned_vector(3, T_A, T_, 0);
> pf->sa_family_list = make_uchar_vector(3, AF_INET, AF_INET6, 0);
> break;
>! } else if (errno == EAFNOSUPPORT || errno == EPROTONOSUPPORT) {
> msg_warn("%s: IPv6 support is disabled: %m", context);
> msg_warn("%s: configuring for IPv4 support only", context);
> /* FALLTHROUGH */
I've just bumped into this exact situation with mail/postfix28 and
suspect that earlier postfix ports have the same issue. The above fix
works on postfix28 and I would request that it be added to that port's
patch list. Since this is a workaround for a FreeBSD-specific issue,
I don't believe it's reasonable to expect Wietse to patch old postfix
variants to work around it.
--
Peter Jeremy
pgpDuvvvy2IWG.pgp
Description: PGP signature
multimedia/linux-realplayer marked BROKEN=unfetchable
but MASTER_SITES= can be changed from unfetchable https://helixcommunity.org/download.php/2479/ to fetchable http://ftp.lip6.fr/pub/linux/distributions/slsoc/5x/i386/i386/SL/ :player \ RealPlayer-10.0.9.809-20070726.i586.rpm ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to handle WITH_CLANG_IS_CC in ports
On 2012-11-25 12:49, Tobias Rehbein wrote:
I am the maintainer of ganes/stonesoup. This port builds fine with gcc.
It also builds with clang, if the MAKE_ARGS are tweaked.
Currently I can check for
${CC:T:M*clang*}
to know if I have to change the MAKE_ARGS for building with clang or
not.
In CURRENT cc is clang and the environment variable CC is no longer set.
This lets the build of games/stonesoup fail. My question is how to
correctly check if cc is clang or not. My first guess was something
along the lines of
${CC:T:M*clang*} || (defined(WITH_CLANG_IS_CC) && ${CC:T:Mcc})
but I guess there is some kind of official way to handle this (ideally
warpped in some Mk macro.
Just check if OSVERSION >= 124, maybe? Or add some logic to
bsd.port.mk that handles this, like was done with pkgng. For example,
introducing a PORTS_COMPILER_TYPE macro like in base.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ editors/jedit | 4.5.2 | 5.0.0 +-+ graphics/ImageMagick| 6.7.9-4 | 6.8.0-6 +-+ graphics/xmedcon| 0.11.1 | 0.12.0 +-+ net/liveMedia | 2012.04.04 | 2012.11.22 +-+ security/polarssl | 1.1.4 | 1.2.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: graphics/OpenEXR: patch for gcc46+
On Sun, 25 Nov 2012 12:00:00 + freebsd-ports-requ...@freebsd.org wrote: > Re: graphics/OpenEXR: patch for gcc46+ This Patch is not needed for new Version graphics/OpenEXR-1.7.1 there is in openexr/openexr-1.7.1/exrenvmap/blurImage.cpp #include #include #include "Iex.h" #include #include #include using namespace std; using namespace Imf; using namespace Imath; On Nov 23, 2012, at 4:27 PM, Andriy Gapon wrote: > --- exrenvmap/blurImage.cpp.orig 2012-11-23 23:23:48.714449156 +0200 > +++ exrenvmap/blurImage.cpp 2012-11-23 23:24:09.765447850 +0200 > @@ -45,6 +45,7 @@ > #include "Iex.h" > #include > #include > +#include > > using namespace std; > using namespace Imf; > > This patch is required because memcpy(3) is used in the file. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
How to handle WITH_CLANG_IS_CC in ports
Hi all,
I am the maintainer of ganes/stonesoup. This port builds fine with gcc.
It also builds with clang, if the MAKE_ARGS are tweaked.
Currently I can check for
${CC:T:M*clang*}
to know if I have to change the MAKE_ARGS for building with clang or
not.
In CURRENT cc is clang and the environment variable CC is no longer set.
This lets the build of games/stonesoup fail. My question is how to
correctly check if cc is clang or not. My first guess was something
along the lines of
${CC:T:M*clang*} || (defined(WITH_CLANG_IS_CC) && ${CC:T:Mcc})
but I guess there is some kind of official way to handle this (ideally
warpped in some Mk macro.
Regards
Tobias
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
