Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Mar 2008 21:37:50 +0300
From:      Ruslan Ermilov <ru@freebsd.org>
To:        Alfred Perlstein <alfred@freebsd.org>
Cc:        cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org
Subject:   Re: cvs commit: src/sys/dev/en midway.c src/sys/dev/fatm if_fatm.c src/sys/dev/firewire if_fwe.c if_fwip.c src/sys/dev/iscsi/initiator isc_soc.c src/sys/kern subr_mchain.c uipc_mbuf.c uipc_socket.c uipc_syscalls.c src/sys/net bpf.c ...
Message-ID:  <20080325183750.GA51894@team.vega.ru>
In-Reply-To: <20080325180152.GB67856@elvis.mu.org>
References:  <200803250939.m2P9d3RC028128@repoman.freebsd.org> <20080325180152.GB67856@elvis.mu.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 25, 2008 at 11:01:52AM -0700, Alfred Perlstein wrote:
> I don't think this was thought out enough, there are times when you
> would want to limit the total memory allocated to mbufs and avoid
> deadlocks in low memory situations.
> 
> Even the old allocator could have been trivially modified to block
> forever upon exhaustion of the mbuf arena.
> 
> The reason why the old allocator was not "fixed" to block forever
> was to allow for recovery from low memory deadlocks.
> 
> A lot of work went into making the system safe in the face of these
> deadlocks and removing it "to clean up" due to a deficiency with
> the current allocator and without understanding why it was there
> in the first place is a mistake.
> 
> This whole thing needs to be backed out.
> 
Are you (or anyone else you know) planning to work on adding real
support for M_TRYWAIT?


Cheers,
-- 
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080325183750.GA51894>