From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ve0-f170.google.com (mail-ve0-f170.google.com [209.85.128.170]) by dpdk.org (Postfix) with ESMTP id 18EDC58E1 for ; Tue, 1 Jul 2014 00:43:19 +0200 (CEST) Received: by mail-ve0-f170.google.com with SMTP id i13so8865185veh.29 for ; Mon, 30 Jun 2014 15:43:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=20LLCsWKq+PHUEibGToayJhpdJESgRwkwdqDc0MYaGc=; b=ZLeQDzcUMMdHaw0RlqoMjJvQ4kNk32DFDKH/TWHigxK1XFO2fEmnv21d5tAtOFyN17 gV/UmO/XvcBWjJBtgjNW2Tc0PZ1xRuvY8bHzlxcoRJHZHjqeg+SPqTjU/rv8b88puzeG YL7JUZDmypxwGaOyoM5yVQ80zDuv2itdSIdVASnmRtSUu+94fomRVB2QveUzFcrirwP4 LyDsdM6LY1flkX3zKKqd1SrJGf60ViotYQBzQmJUxNFNRWOCw2j1B95/eySSvxATOb9n Qnrb8lU6CqjJa9uRd6n4NdqVTY7O+bzPLUGq1soSSyn+H9nlN76U9vFVtxdVzsdMizp5 kQlQ== X-Gm-Message-State: ALoCoQlvjdtsxw9vpC1ddvanF6Vk6g9J0cn1ts8Ke1a+h/CO1WrxuUtZufcnBrGLQ0ZD7P4YasOo MIME-Version: 1.0 X-Received: by 10.58.245.194 with SMTP id xq2mr40806824vec.26.1404168219610; Mon, 30 Jun 2014 15:43:39 -0700 (PDT) Received: by 10.58.3.98 with HTTP; Mon, 30 Jun 2014 15:43:39 -0700 (PDT) Date: Mon, 30 Jun 2014 17:43:39 -0500 Message-ID: From: Matt Laswell To: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Ability to/impact of running with smaller page sizes 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: Mon, 30 Jun 2014 22:43:20 -0000 Hey Folks, In my application, I'm seeing some design considerations in a project I'm working on that push me towards the use of smaller memory page sizes. I'm curious - is it possible in practical terms to run DPDK without hugepages? If so, does anybody have any practical experience (or a back-of-the-envelop estimate) of how badly such a configuration would hurt performance? For sake of argument, assume that virtually all of the memory being used is in pre-allocated mempools (e.g lots of rte_mempool_create(), very little rte_malloc(). Thanks in advance for your help. -- Matt Laswell