Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon

on 07/09/2010 13:38 Vadim Goncharov said the following:
Just to clarify things a little for those following it: the original I4B code
was removed for entirely practical reasons: it couldn't run without the Giant
lock, and support for the Giant lock over the network stack was removed.

But if it was used, removing a component just because of Giant lock is not
practical and is purely ideologic, isn't it?

Which part of "support for the Giant lock *over the network stack* was removed"
[emphasis mine] do you not understand?
The reason is performance for overall network stack, not ideology.

BTW, there were advanced notices for users, request for volunteers, etc.

So, if you didn't speak up at that time please keep silence now :-)

P.S. why is security@ in cc: ?

--
Andriy Gapon
_______________________________________________
freebsd-security@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Policy for removing working code (Was: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon)
    ... removing a component just because of Giant lock ... Which part of "support for the Giant lock *over the network stack* was ... It is not in notices & volunteers, ...
    (freebsd-stable)
  • Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
    ... was removed for entirely practical reasons: it couldn't run without the Giant ... and support for the Giant lock over the network stack was removed. ... removing a component just because of Giant lock is not ... The reason is performance for overall network stack, ...
    (freebsd-stable)
  • Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
    ... On 09/07/2010 02:31 PM, Vadim Goncharov wrote: ... and support for the Giant lock over the network stack was ... The situation was that in order to take performance of the network stack as a whole up to the next level it was necessary to remove the Giant lock. ...
    (freebsd-stable)
  • Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
    ... On 09/07/2010 02:31 PM, Vadim Goncharov wrote: ... and support for the Giant lock over the network stack was ... The situation was that in order to take performance of the network stack as a whole up to the next level it was necessary to remove the Giant lock. ...
    (FreeBSD-Security)
  • Running the network stack without Giant -- change in default coming
    ... it's now possible to run large parts of the network stack in ... Giant lock turned on. ... device drivers are not able to run without the Giant lock. ... by disabling Giant. ...
    (freebsd-current)