On Tue, 4 Jul 2006, CaT wrote:
On Fri, Jun 30, 2006 at 08:50:39AM +1000, CaT wrote:
Another datapoint to this is that I've had this my netcat web test
running since 8:42pm yesterday. It's 8:37am now. It hasn't progressed
in any way. It hasn't quit. It hasn't timed out. It just sits there,
On Mon, 5 Jun 2006, Adrian Bunk wrote:
On Mon, Jun 05, 2006 at 08:52:35AM -0400, Jeff Garzik wrote:
...
Paying attention to proper reverse engineering is good. Being
overzealous is not.
Being overzealous about merging drivers without first checking the legal
ramifications is a good way to
On Mon, 24 Apr 2006, Auke Kok wrote:
linux-os (Dick Johnson) wrote:
On Mon, 24 Apr 2006, Auke Kok wrote:
Ingo Oeser wrote:
On Saturday, 22. April 2006 15:49, Jörn Engel wrote:
That was another main point, yes. And the endpoints should be as
little burden on the bottlenecks as possible
On Mon, 24 Apr 2006, Auke Kok wrote:
Ingo Oeser wrote:
On Saturday, 22. April 2006 15:49, Jörn Engel wrote:
That was another main point, yes. And the endpoints should be as
little burden on the bottlenecks as possible. One bottleneck is the
receive interrupt, which shouldn't wait for
On Mon, 24 Apr 2006, Rick Jones wrote:
Thats right. This will be made a non issue with early demuxing
on the NIC and MSI (or was it MSI-X?) which will select
the right CPU based on hardware channels.
MSI-X. with MSI you still have only one cpu handling all MSI interrupts and
that doesn't
On Tue, 14 Mar 2006, Bart Samwel wrote:
linux-os (Dick Johnson) wrote:
On Mon, 13 Mar 2006, Greg Scott wrote:
Bst... Not! There are not any MAC addresses associated with any
of the intercity links, usually not even in WANs! MAC is for
Ethernet! Once you go to fiber, ATM, T-N, etc
On Mon, 13 Mar 2006, Stephen Hemminger wrote:
There still is a bug in the 3c59x driver. It doesn't include any code
to handle changing the mac address. It will work if you take the device
down, change address, then bring it up. But you shouldn't have to do that.
Also, if the driver
On Mon, 13 Mar 2006, Greg Scott wrote:
But in a failover scenario you want two devices to have the same IEEE
(station) Address (or MAC Address or hardware address). So many names
for the same thing!
When the primary unit fails, you want the backup unit to completely
assume the failed
I have to
spend some money with the IEEE soon to support lots and lots of
rollouts. :)
- Greg Scott
-Original Message-
From: Rick Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, March 13, 2006 3:50 PM
To: linux-os (Dick Johnson)
Cc: Greg Scott; Chuck Ebbert; linux-kernel; netdev
On Fri, 2 Dec 2005, Al Boldi wrote:
The current ip / ifconfig configuration is arcane and inflexible. The reason
being, that they are based on design principles inherited from the last
century.
In a GNU/OpenSource environment, OpenMinds should not inhibit themselves
achieving new
10 matches
Mail list logo
