Date: Sat, 27 Oct 2018 12:22:00 +0530 From: Steevan Rodrigues <steevanxperia@gmail.com> To: rysto32@gmail.com Cc: freebsd-hackers@freebsd.org Subject: Re: Contigfree takes too much time that cuases PCIe driver unload to take up to 30 minutes Message-ID: <CAKsGTHTQT6te47Z4VwXN76LhRmcEDABW%2Bax-am0r%2B47ZkTy5kg@mail.gmail.com> In-Reply-To: <CAFMmRNw7g8pPCYwJmh0yjHnm2XKRgb1d4dPDuPf6gFwnOyZxeQ@mail.gmail.com> References: <CAKsGTHS_KRFBX5qzXe3QcBKavf0GNk0iyOWYjqpi_6dTE_NwCA@mail.gmail.com> <CAKsGTHQs49k8iRSO=pJyo-01q-CVBgAXd1pfopH52FSpNqj9oQ@mail.gmail.com> <CAFMmRNw7g8pPCYwJmh0yjHnm2XKRgb1d4dPDuPf6gFwnOyZxeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes , it is contigfree that is taking too much time. ( Contigfree is taking almost 5x to 10x more time than contigmalloc ) However, I see this issue only on a SuperMicro Server which has Xeon Gold CPU with 10 cores ( dual CPU i.e total 20 cores). So I am wondering whether FreeBSD has performance issues on mutlicore ( more than 16 cores) servers ? Has anyone come across issues like this? Thanks Steevan On Fri, Oct 5, 2018 at 11:31 PM Ryan Stone <rysto32@gmail.com> wrote: > I'm not sure why configfree() would be taking a long time, but > configmalloc() can be extraordinarily expensive when it needs to > defragment memory to meet the request. Does your application really > require a lot of physically contiguous memory? if you can restructure > to not require contigmalloc() all -- maybe by using S/G DMA -- you may > find your life significantly easier. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKsGTHTQT6te47Z4VwXN76LhRmcEDABW%2Bax-am0r%2B47ZkTy5kg>