Re: Policy for removing working code (Was: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon)

2010-09-09 Thread jhell
On 09/08/2010 06:44, Vadim Goncharov wrote: Hi Mark Linimon! On Wed, 8 Sep 2010 07:30:19 +; Mark Linimon wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': The reason is performance for overall network stack, not ideology. For a practical reasons, it works but slow

Policy for removing working code (Was: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon)

2010-09-08 Thread Vadim Goncharov
Hi v...@freebsd.org! On Wed, 08 Sep 2010 07:01:55 +0200; v...@freebsd.org wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': On 09/07/10 23:31, Vadim Goncharov wrote: 07.09.10 @ 18:53 Andriy Gapon wrote: The reason is performance for overall network stack, not ideology. For

Policy for removing working code (Was: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon)

2010-09-08 Thread Vadim Goncharov
Hi Doug Barton! On Tue, 07 Sep 2010 20:37:07 -0700; Doug Barton wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': On 09/07/2010 02:31 PM, Vadim Goncharov wrote: 07.09.10 @ 18:53 Andriy Gapon wrote: on 07/09/2010 13:38 Vadim Goncharov said the following: Just to clarify

Policy for removing working code (Was: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon)

2010-09-08 Thread Vadim Goncharov
Hi Mark Linimon! On Wed, 8 Sep 2010 07:30:19 +; Mark Linimon wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': The reason is performance for overall network stack, not ideology. For a practical reasons, it works but slow is better than doesn't work at all (due to

Re: Policy for removing working code (Was: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon)

2010-09-08 Thread John Baldwin
On Wednesday, September 08, 2010 6:24:11 am Vadim Goncharov wrote: Because the original I4B code didn't work without the Giant lock, and because no one stepped forward to fix that, the code had to be removed. No. The code needn't removal, the stack should be modified to be fast without