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
On 14.09.2013 22:49, Olivier Cochard-Labbé wrote:
On Sat, Sep 14, 2013 at 4:28 PM, Luigi Rizzo 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 same
src/dst port).
Th
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 sh
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 packet
Hello list!
There is a lot constantly raising discussions related to networking
stack performance/changes.
I'll try to summarize current problems and possible solutions from my
point of view.
(Generally this is one problem: stack is slooow,
but we need to know why an
Hello list.
We currently have VLAHWFILTER functionality allowing underlying
physical/virtual interfaces to be aware of vlans stacked on them.
However, this knowledge is only used to program NIC hw filter (or to
broadcast to member ifaces in lagg case).
Proposed idea is to save vlan ifp pointer i
Hello list!
Today more and more NICs are capable of splitting traffic to different
Rx/TX rings permitting OS to dispatch this traffic on different CPU
cores. However, there are some problems that arises from using multi-nic
(or even singe multi-port NIC) configurations:
Typical (OS) question
On 09.11.2012 13:59, Fabien Thomas wrote:
Le 9 nov. 2012 à 10:05, Alexander V. Chernikov a écrit :
On 09.11.2012 12:51, Fabien Thomas wrote:
Le 8 nov. 2012 à 11:25, Alexander V. Chernikov a écrit :
On 08.11.2012 14:24, Andre Oppermann wrote:
On 08.11.2012 00:24, Alexander V. Chernikov
On 09.11.2012 12:51, Fabien Thomas wrote:
Le 8 nov. 2012 à 11:25, Alexander V. Chernikov a écrit :
On 08.11.2012 14:24, Andre Oppermann wrote:
On 08.11.2012 00:24, Alexander V. Chernikov wrote:
Hello list!
Currently we need to acquire 2 read locks to perform simple 6-byte
copying from arp
On 08.11.2012 03:46, Adrian Chadd wrote:
On 7 November 2012 15:24, Alexander V. Chernikov wrote:
Hello list!
Currently we need to acquire 2 read locks to perform simple 6-byte copying
from arp record to packet ethernet header.
It seems that acquiring lle lock for fast path (main traffic flow
On 08.11.2012 14:24, Andre Oppermann wrote:
On 08.11.2012 00:24, Alexander V. Chernikov wrote:
Hello list!
Currently we need to acquire 2 read locks to perform simple 6-byte
copying from arp record to packet
ethernet header.
It seems that acquiring lle lock for fast path (main traffic flow
Hello list!
Currently we need to acquire 2 read locks to perform simple 6-byte
copying from arp record to packet ethernet header.
It seems that acquiring lle lock for fast path (main traffic flow) is
not necessary even with current code.
My tests shows ~10% improvement with this patch appli
On 04.07.2012 00:27, Luigi Rizzo wrote:
On Tue, Jul 03, 2012 at 09:37:38PM +0400, Alexander V. Chernikov wrote:
...
Thanks, another good point. I forgot to merge this option from andre's
patch.
Another 30-40-50kpps to win.
not much gain though.
What about the other IPSTAT_INC counters ?
On 03.07.2012 20:55, Luigi Rizzo wrote:
On Tue, Jul 03, 2012 at 08:11:14PM +0400, Alexander V. Chernikov wrote:
Hello list!
I'm quite stuck with bad forwarding performance on many FreeBSD boxes
doing firewalling.
...
In most cases system can forward no more than 700 (or 1400) kpps whi
Hello list!
I'm quite stuck with bad forwarding performance on many FreeBSD boxes
doing firewalling.
Typical configuration is E5645 / E5675 @ Intel 82599 NIC.
HT is turned off.
(Configs and tunables below).
I'm mostly concerned with unidirectional traffic flowing to single
interface (e.g. us
On 08.06.2012 11:20, Jonathan McKeown wrote:
On Thursday 07 June 2012 17:00:04 Alexander V. Chernikov wrote:
Hello list!
Since the early days ifconfig(8) has the following functionality:
[hostname in place of literal address]
Moreover, ifconfig em0 some_valid_fqdn/MASK silently ignores it
Hello list!
Since the early days ifconfig(8) has the following functionality:
..
address
For the DARPA-Internet family, the address is either a
host name
present in the host name data base, hosts(5), or a DARPA
Internet
address expressed in the Inte
On 07.09.2011 11:17, Julian Elischer wrote:
On 7/16/11 5:43 AM, Vlad Galu wrote:
Hello,
Hello!
A couple of years ago, Stef Walter proposed a patch[1] that enforced
the scope of routing messages. The general consesus was that the best
approach would be the OpenBSD way - transporting the FIB nu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hiroki Sato wrote:
> Vlad Galu wrote
> in :
>
> du> Hello,
> du>
> du> A couple of years ago, Stef Walter proposed a patch[1] that enforced
> du> the scope of routing messages. The general consesus was that the best
> du> approach would be the Open
On 12.07.2011 11:10, Garrett Cooper wrote:
On Mon, Jul 11, 2011 at 11:16 PM, Alexander V. Chernikov
wrote:
Garrett Cooper wrote:
Hi,
While trying to determine how to print out routes via kvm for
net-snmp, I noticed that there's a chunk of code from the 4.4 BSD Lite
days that
Garrett Cooper wrote:
> Hi,
> While trying to determine how to print out routes via kvm for
> net-snmp, I noticed that there's a chunk of code from the 4.4 BSD Lite
> days that isn't executed in netstat as NewTree is always 0. The
> following patch removes that dead code and gets the FreeBSD so
Yuri wrote:
When I am trying to understand how Elf executable works I am only getting to few
pages with very fragmentary information.
Googling many constants like R_386_PC32, R_386_TLS_LD only yields some
discussion references and code.
Anybody knows where to read more about the Elf format? Doe
22 matches
Mail list logo