Date: Wed, 12 Feb 2014 15:36:38 -0800 From: Adrian Chadd <adrian@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Garrett Wollman <wollman@freebsd.org>, Navdeep Parhar <np@freebsd.org>, "net@freebsd.org" <net@freebsd.org> Subject: Re: Use of contiguous physical memory in cxgbe driver Message-ID: <CAJ-VmokDb4dkhzO6NnYrFKKV2g-bau8H47h2g=wOkvGcqYzRow@mail.gmail.com> In-Reply-To: <201402121446.19278.jhb@freebsd.org> References: <21216.22944.314697.179039@hergotha.csail.mit.edu> <201402111348.52135.jhb@freebsd.org> <CAJ-VmonCdNQPUCQwm0OhqQ3Kt_7x6-g-JwGVZQfzWTgrDYfmqw@mail.gmail.com> <201402121446.19278.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 February 2014 11:46, John Baldwin <jhb@freebsd.org> wrote: > Is this because UMA keeps lots of mbufs cached in your workload? The physmem > buddy allocator certainly seeks to minimize fragmentation. However, it can't > go yank memory out of UMA caches to do so. I'll ask you on irc, but where's that happening? My read of the code is that once it grabs a larger page and fragments it, it's lost. -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokDb4dkhzO6NnYrFKKV2g-bau8H47h2g=wOkvGcqYzRow>