Date: Sun, 26 Jan 1997 15:23:16 +1100 (EST) From: proff@suburbia.net To: hackers@freebsd.org Subject: SLAB stuff, and applications to current net code (fwd) Message-ID: <19970126042316.10096.qmail@suburbia.net>
next in thread | raw e-mail | index | archive | help
> From owner-netdev@roxanne.nuclecu.unam.mx Sun Jan 26 04:12:46 1997 > Delivered-To: proff@suburbia.net > Date: Sat, 25 Jan 1997 22:47:23 -0500 > Message-Id: <199701260347.WAA07788@jenolan.caipgeneral> > From: "David S. Miller" <davem@jenolan.rutgers.edu> > To: netdev@roxanne.nuclecu.unam.mx > Subject: SLAB stuff, and applications to current net code > Sender: owner-netdev@roxanne.nuclecu.unam.mx > Precedence: bulk > Reply-To: netdev@roxanne.nuclecu.unam.mx, > "David S. Miller" <davem@jenolan.rutgers.edu> > > I'm going to try feveriously to get the SLAB allocator integrated into > Linus's sources over the next two days. For the most part my > incentive is so that people think about it when they design memory > object allocation subsystems. > > For example, even right now, look at the way struct sock's are indeed > allocated. Alan's recent change to add sock_init_data() and the fact > that my sources already use SLAB for struct sock sparked this idea. > > We could in this case just make sock_init_data() the constructor > routine for the sock SLAB. So for a warm SLAB cache this code never > gets run as long as users of sock's are not forgetful and leave a sock > in a reasonable state when they free them. (ie. don't leave crap on > the receive queue etc.) > Can anyone inform me what a SLAB allocator is, and if so, would freebsd benefit from one? Cheers, Julian.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970126042316.10096.qmail>