On Wed, Feb 11, 2009 at 8:25 AM, Andriy Gapon wrote:
> on 10/02/2009 22:43 Aniruddha Bohra said the following:
>> You can see Click: http://read.cs.ucla.edu/click/
>> It does not run on FreeBSD >4.
>> I have an old diff which builds on the work by Marko Zec and Bruce
&g
You can see Click: http://read.cs.ucla.edu/click/
It does not run on FreeBSD >4.
I have an old diff which builds on the work by Marko Zec and Bruce
Simpson, that allows me to load the click module.
http://www.cs.rutgers.edu/~bohra/click-1.5.0.diff
Hope this helps
Aniruddha
___
On Thu, 2006-03-02 at 13:28 -0800, Kip Macy wrote:
> -CURRENT runs on 3.0 as a domU. There is partial dom0 support. The
> changes have not gone back into the mainline because xenbus is
> extremely difficult to integrate cleanly. You can check on the state
> of the xen3 branch in perforce.
At sever
Greg 'groggy' Lehey wrote:
Last week, at the Linux.conf.au in Dunedin, Van Jacobson presented
some slides about work he has been doing rearchitecting the Linux
network stack. He claims to have reduced the CPU usage by 80% and
doubled network throughput (he expects more, but it was limited by
me
I'll get my self informed by reading those papers then i'll have some
comments and questions if you dont mind.
Questions are always welcome
although ,i want to know , when you said
If you mean network level, then TCP provides that,
maybe you are talking about timeouts in TCP/IP ?
TCP retransmi
Hello,
I see what you mean , you are talking at higher level ,
when i mentioned Robust TCP/IP i meant TCP connections in the kernel
network stack level ,
the architecture you are talking about is like a middle ware handeling
all TCP/IP connections for a client to multiple servers.
the mechanism is
i was thinking about implementing Robust TCP/IP connections .. but
somebody told me that is not very consistent , and i think so also ,
Did you consider fault-tolerant TCP/IP connections to multiple servers?
See these :
This one is heavy-weight, whole process wrapping etc.
Also the implemen
Hello,
The one setting that I do suggest you keep is:
kern.ipc.somaxconn=512 (128 may be too low for http testing)
In our experience with Apache and clients that do not use
Keep Alive (are short lived), 512 is also very low. It
causes listen queue overflows and leads to a very low
throughput.
Ano
Hello,
I was wondering if there is a standard
header file that implements the RFC 1982 ?
It basically defines serial numbers and the
arithmetic operations on them.
All it does is :
s' = (s + n) modulo (2 ^ SERIAL_BITS)
i1 is the arithmetic integer whose value is
the same as s1, and
Hello,
I am writing a loadable kernel module where I
need a per-cpu region of wired memory. The module should
work for -current and -stable.
How can I get such a region of memory?
Any docs or pointers would be great.
Thanks
Aniruddha
___
Somebody is again subscribing hackers to several
lists..
Again a disgruntled member maybe ...
Is there any way to stop this ?
Aniruddha
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send an
As always, you're seeing the lack of available committer time, not a real
lack of interest. One way to accelerate the process might be for someone
(not necessarily you, any reader of this mailing list could do it) to show
that this change visibly benefits some easy to run benchmark. Some simple
s
Hello
The following code snippet is from netinet/tcp_usrreq.c
As in the comment (and presumably correct behaviour) a RST should
be sent on close if the connection is embryonic. However,
if (tp->t_state < TCPS_ESTABLISHED)
tp = tcp_close(tp);
does not do it. One can imagine a scenario when a
13 matches
Mail list logo
