From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent JARDIN Subject: Re: [PATCH 3/7] optimize log/panic Date: Wed, 05 Jun 2013 16:34:42 +0200 Message-ID: <51AF4C82.2010603@6wind.com> References: <20130530171234.301927271@vyatta.com> <20130530171626.884622340@vyatta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: <20130530171626.884622340-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On 30/05/2013 19:12, Stephen Hemminger wrote: > Both logging and calls to panic are never in the critical path. > Use the GCC attribute cold to mark these functions as cold, > which generates more optimised code. > > Signed-off-by: Stephen Hemminger Reviewed-by: Vincent Jardin It does not hurt to move both to a cold section. TODO: some other init and setup functions should be cold too.