Re: Importing iSCSI target from NetBSD

From: Peter Jeremy <peterjeremy@xxxxxxxxxxxxxxxx>
Date: Wed, 31 May 2006 17:23:04 +1000

On Tue, 2006-May-30 09:46:39 +0100, Robert Watson wrote:

network bandwidth. It seems like hardware swings back and forth quite a
bit -- for a few years gigabit was way-the-heck-faster-than-CPU, now it's
the other way around again. The best stack optimization work happens when
you have to figure out how to get the network stack to perform well in
near-infinite bandwidth scenarios with a CPU-bound stack,

Can't you get this by using a gigabit interface and throttling the
CPU via ACPI or cpufreq?

--
Peter Jeremy
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Follow-Ups:
- Re: Importing iSCSI target from NetBSD
  - From: Robert Watson
- Re: Importing iSCSI target from NetBSD
  - From: Maxim Sobolev

References:
- Importing iSCSI target from NetBSD
  - From: Maxim Sobolev
- Re: Importing iSCSI target from NetBSD
  - From: F. Senault
- Re: Importing iSCSI target from NetBSD
  - From: Scott Long
- Re: Importing iSCSI target from NetBSD
  - From: Maxim Sobolev
- Re: Importing iSCSI target from NetBSD
  - From: Maxim Sobolev
- Re: Importing iSCSI target from NetBSD
  - From: Scott Long
- Re: Importing iSCSI target from NetBSD
  - From: Paul Allen
- Re: Importing iSCSI target from NetBSD
  - From: Brooks Davis
- Re: Importing iSCSI target from NetBSD
  - From: Robert Watson

Prev by Date: Re: FreeBSD's embedded agenda - summary
Next by Date: Re: Importing iSCSI target from NetBSD
Previous by thread: Re: Importing iSCSI target from NetBSD
Next by thread: Re: Importing iSCSI target from NetBSD
Index(es):
- Date
- Thread

Relevant Pages

Re: [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCPportsfrom the host TCP port space.
... And actually RDMA stack exist and no one said it should be thrown away ... What will happen if hardware RDMA connection got terminated and software ... but how it influence to the network stack is. ...
(Linux-Kernel)
Re: HEADS UP: debug.mpsafenet behavior changing! (turn it off)
... This is a reminder e-mail! ... stack, and will now start pushing Giant into socket-related system calls. ... > If set, don't hold Giant over any of the network stack, including the ...
(freebsd-current)
Re: Importing iSCSI target from NetBSD
... On Wed, 31 May 2006, Peter Jeremy wrote: ... The best stack optimization work happens when ... I suspect there's also a motivation element to the yet bigger, yet newer performance numbers, which simply wouldn't be replicated by successfully transfering 100mbps using a quad opteron :-). ...
(freebsd-current)
Re: ng_ksocket on CURRENT
... > the network stack. ... Giant should be held for all of this. ... Do you know of a way the stack trace below ...
(freebsd-current)
Removing the native Wind River Network Stack and replacing with 3rd party stack
... replace it with a 3rd party stack. ... according to the vendor is far less in size than the native Wind River ... Our image with just the native WRS network stack was around 750 ...
(comp.os.vxworks)