I'm experimenting with a new way to track -CURRENT
by using Crochet to build successive VMWare VM images.
Each new VM can then be used to build the next one.
I'm specifically using this with VMWare Fusion on Mac OS,
but it should work with Linux or FreeBSD VMWare hosts
as well.
Here's an outline
On 29.08.2013 02:24, Andre Oppermann wrote:
On 28.08.2013 20:30, Alexander V. Chernikov wrote:
Hello list!
Hello Alexander,
Hello Andre!
I'm very sorry to answer so late.
you sent quite a few things in the same email. I'll try to respond
as much as I can right now. Later you should split
On 29.08.2013 05:32, Slawa Olhovchenkov wrote:
On Thu, Aug 29, 2013 at 12:24:48AM +0200, Andre Oppermann wrote:
..
while Intel DPDK claims 80MPPS (and 6windgate talks about 160 or so) on the
same-class hardware and
_userland_ forwarding.
Those numbers sound a bit far out. Maybe if the
On 14.09.2013 22:49, Olivier Cochard-Labbé wrote:
On Sat, Sep 14, 2013 at 4:28 PM, Luigi Rizzo ri...@iet.unipi.it wrote:
IXIA ? For the timescales we need to address we don't need an IXIA,
a netmap sender is more than enough
The great netmap generates only one IP flow (same src/dst IP and
On Mon, Sep 23, 2013 at 12:01:17AM +0400, Alexander V. Chernikov wrote:
On 29.08.2013 05:32, Slawa Olhovchenkov wrote:
On Thu, Aug 29, 2013 at 12:24:48AM +0200, Andre Oppermann wrote:
..
while Intel DPDK claims 80MPPS (and 6windgate talks about 160 or so) on
the same-class hardware
On 29.08.2013 15:49, Adrian Chadd wrote:
Hi,
Hello Adrian!
I'm very sorry for the looong reply.
There's a lot of good stuff to review here, thanks!
Yes, the ixgbe RX lock needs to die in a fire. It's kinda pointless to
keep locking things like that on a per-packet basis. We should be able
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or legacy at various stages). It
appears that that's not the case, and ${SHELL} is whatever comes from
the environment, which
On 9/22/2013 6:18 PM, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or legacy at various stages). It
appears that that's not the case, and ${SHELL} is
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or legacy at various stages). It
appears that that's not the
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set to the right copy
of /bin/sh (like maybe the one in tmp or
On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote:
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a makefile? I had
assumed the ${SHELL} variable would be set
On Sun, 2013-09-22 at 19:45 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote:
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
What's the right way to launch the bourne shell from a
On Sun, Sep 22, 2013 at 05:56:07PM -0600, Ian Lepore wrote:
You can hard-code /bin/sh directly, but what I was getting at with the
'#!/usr/bin/env sh' is that the 'sh' interpreter of the build
environment could be used (instead of /bin/sh directly). Then you don't
need to worry about the
Hi!
On 22 September 2013 13:12, Alexander V. Chernikov
melif...@yandex-team.ruwrote:
I'm thinking the same way, but we're stuck with 'forwarding lookup' due
to problem with egress interface pointer, as I mention earlier. However it
is interesting to see how much it helps, regardless of
14 matches
Mail list logo
