Re: locking & iovecs
From: Robert Watson (rwatson_at_freebsd.org)
Date: 09/24/04
- Previous message: Pekka Savola: "Re: (KAME-snap 8792) Re: Weird memory exhaustion with FreeBSD 4.10-STABLE"
- In reply to: Waldemar Kornewald: "Re: locking & iovecs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 24 Sep 2004 14:08:55 -0400 (EDT) To: Waldemar Kornewald <Waldemar.Kornewald@web.de>
On Fri, 24 Sep 2004, Waldemar Kornewald wrote:
> > Once GIANT is really gone, it may be nearly that easy. We're a ways
> > from that though.
>
> So, the code is not fully thread-safe yet (we want to drop GIANT)? Then,
> I misunderstood something. Will 5.3 be freed of GIANT?
Including some components in the kernel will force the Giant lock back
over the network stack. For example, if you compile with KAME IPSEC or
IPX. There is active work in many of those areas to remove that
requirement.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org Principal Research Scientist, McAfee Research
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
- Previous message: Pekka Savola: "Re: (KAME-snap 8792) Re: Weird memory exhaustion with FreeBSD 4.10-STABLE"
- In reply to: Waldemar Kornewald: "Re: locking & iovecs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]