Old Synopsis: network problems under -current, nfe(4) and jumbo packets
New Synopsis: [nfe]: network problems under -current, nfe(4) and jumbo packets
Responsible-Changed-From-To: freebsd-bugs-freebsd-net
Responsible-Changed-By: remko
Responsible-Changed-When: Fri Sep 21 06:14:55 UTC 2007
Old Synopsis: Solid hang with bge interface
New Synopsis: [bge]: Solid hang with bge interface
Responsible-Changed-From-To: freebsd-bugs-freebsd-net
Responsible-Changed-By: remko
Responsible-Changed-When: Fri Sep 21 06:15:58 UTC 2007
Responsible-Changed-Why:
Reassign to networking team
On Thu, 20 Sep 2007 23:54:49 -0400
Richard A Steenbergen [EMAIL PROTECTED] wrote:
Honestly, FreeBSD routing code is pretty poor as far as a modern router
goes. If you throw enough CPU at it you can brute force your way through
plenty of things, but in the context of modern commercial routers
I'm not saying you should use polling. I'm saying that not using polling
makes for more context switches. 64bit registers are twice as large as
32bit registers. There will be a bigger penalty on stack/memory usage
and therefore slower transitions from one context to another (read:
handling a
Folks have been asking about XORP in this thread.
XORP can take a full BGP feed just fine as long as you have enough
memory.; for a full default-free-zone feed, you are looking at in the
region of 1GB - 1.5GB, perhaps less if you use aggregation.
If you look at the NSDI '05 paper you'll see
On Fri, Sep 21, 2007 at 04:52:05PM +0100, Bruce M. Simpson wrote:
Folks have been asking about XORP in this thread.
XORP can take a full BGP feed just fine as long as you have enough
memory.; for a full default-free-zone feed, you are looking at in the
region of 1GB - 1.5GB, perhaps less
Date: Thu, 20 Sep 2007 18:28:30 -0700
From: Alfred Perlstein [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
* Yuri Lukin [EMAIL PROTECTED] [070920 16:49] wrote:
On Thu, 20 Sep 2007 00:24:09 -0700, Alfred Perlstein wrote
Juniper is based on FreeBSD. ;-)
On old code from the 4.x
Date: Fri, 21 Sep 2007 21:46:02 +1000
From: Norberto Meijome [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Thu, 20 Sep 2007 23:54:49 -0400
Richard A Steenbergen [EMAIL PROTECTED] wrote:
Honestly, FreeBSD routing code is pretty poor as far as a modern router
goes. If you throw enough
On Fri, Sep 21, 2007 at 09:46:02PM +1000, Norberto Meijome wrote:
Richard A Steenbergen [EMAIL PROTECTED] wrote:
Honestly, FreeBSD routing code is pretty poor as far as a modern router
goes. If you throw enough CPU at it you can brute force your way through
plenty of things, but in the
We are seeing an intermittent problem with FreeBSD 6.2 and our
custom web server application, where incoming listens will
sometimes not be passed to our application to be accepted. It is as
if the listen queue is clogged somehow, and all incoming listens
are blocked from being passed to our
On 9/20/07, Christopher Chen [EMAIL PROTECTED] wrote:
On 9/20/07, Max Laier [EMAIL PROTECTED] wrote:
On Thursday 20 September 2007, Christopher Chen wrote:
Hi:
I'm running 6.2-RELEASE on some Pentium D's running and amd64 port.
I'm doing some mildly interesting things with vlan
This drew a blank in -questions. I don't know where else to post it, so
I'm hoping someone here might be able to spare me a clue.
We're building a small board with two AVR Tiny MCUs chatting to each
other over an opto-isolated I2C-compatible bus, hopefully at 400kbps.
Hoping to use the
12 matches
Mail list logo
