From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id C318A5A15 for ; Thu, 22 Jan 2015 05:45:37 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 3050380D360; Wed, 21 Jan 2015 20:45:32 -0800 (PST) Date: Wed, 21 Jan 2015 20:45:32 -0800 From: Matthew Hall To: Linhaifeng Message-ID: <20150122044531.GA13230@mhcomputing.net> References: <54C070DF.1050006@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54C070DF.1050006@huawei.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] some questions about rte_memcpy X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 04:45:38 -0000 On Thu, Jan 22, 2015 at 11:39:11AM +0800, Linhaifeng wrote: > Why call memcpy when n is constant variable? One theory. Many DPDK functions crash if they are called before rte_eal_init() is called. So perhaps this could be a cause, since that won't have been called when working on a constant? Matthew.