From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f193.google.com (mail-pg1-f193.google.com [209.85.215.193]) by dpdk.org (Postfix) with ESMTP id E7E352BC1 for ; Mon, 20 Aug 2018 17:06:40 +0200 (CEST) Received: by mail-pg1-f193.google.com with SMTP id f14-v6so6910629pgv.13 for ; Mon, 20 Aug 2018 08:06:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=uqYYf7pTo2Ek0c67NbvVB/KRuYDSo4Z/tnSBtY09j/0=; b=rrIeZLGkEbPeTE014D9/Wtl9+H2gjgbG/Eb21zQ9f9XATB+6MCAqEbfferGL4Xzebo ETRoTRJbdHLH7SrhhhU97jN0Au0OBc7CR2N0FNNS2/cVUgfZK6Zp5C0tfCzzieYMFBwz 0sJhL3juZMHC9gX8+7YiI4EauEoCVzbR6gqX4UtTOxOQfX35JS65Y5XhDOnL1Zv33+/b vZVOQSiXHTTkBA33ko/hnImoF71ZeEtdVcHBJbR0E49rT8jupXxL4srWPWlQqvg5dyme DQuKJlfBo+FO72ST7Q14R9IpU2XjsbH6sQTuE45duxRgiSwyd5AICgdy37KCMj5/zcGZ nFaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=uqYYf7pTo2Ek0c67NbvVB/KRuYDSo4Z/tnSBtY09j/0=; b=LmUxcjLLpTbYQdJum5ek9ksAu7sinSfUx5R9vMZcqzr7X93dpuM+wxXsMzcyfv4yY0 lP7IxPncBL2HLtD1CIqjSRpX5E7Ao3WATRtF6/oiA8oRAerdICVuV5PC2oT6QPYIf/4V yGAQ73u7dcuZA+XbxepZMsEsvmBKKcfeY/t71lffTrLuBtleFMhBDOCE/kQbtBJvM5eO T9yUpWds0rTqzli2EpEePU59fnaNyugmrKR9NfXIj5QWswc/RYQ30Y9HdRkw1MUvNMaV UGcIL0hrwtSsCMoU0cA5k2lnhTjF4GVf59iuseheKnzHeyyCs/eL5e7EXzOxqK5KTtww UUUg== X-Gm-Message-State: AOUpUlFact03wInWDowU+FQC8uHqR7Qt3X5uV/eWf/fNtskgFHVBbOFd 7cbOcV9CGucmN75/JRSv9PmMvQ== X-Google-Smtp-Source: AA+uWPz52+7H2pj1x7T9r3iEvxzC1z2lKEZSJOMzwsrVH2SwEvdGsjQodKC2LkPbyTT2dfcvMyVWLQ== X-Received: by 2002:a62:4b48:: with SMTP id y69-v6mr48568520pfa.93.1534777599882; Mon, 20 Aug 2018 08:06:39 -0700 (PDT) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id c1-v6sm21321335pfg.25.2018.08.20.08.06.39 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 20 Aug 2018 08:06:39 -0700 (PDT) Date: Mon, 20 Aug 2018 08:06:36 -0700 From: Stephen Hemminger To: Kevin Wilson Cc: dev@dpdk.org Message-ID: <20180820080636.2d77daeb@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] Minimum kernel version for DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2018 15:06:41 -0000 On Mon, 20 Aug 2018 11:46:25 +0300 Kevin Wilson wrote: > Hi all, > Maybe this is a silly question, please bear with me. >=20 > According to the =E2=80=9CGetting Started Guide for Linux=E2=80=9D in > http://doc.dpdk.org/guides/linux_gsg/sys_reqs.html, > the kernel version should be >=3D 3.2. > Accrding to my understanding, there are only two kernel modules in DPDK, > namely rte_kni.ko and igb_iuo.ko. > Instead of igb_uio.ko I intend to use uio_pci_generic.ko for binding the = device. >=20 > I want to work with DPDK with kernel 3.1, without using rte_kni and no ig= b_uio > as mentioned. >=20 > Won't the DPDK code compile for such a kernel ? won't it work ? >=20 > Regards, > Kevin I would never build and deploy an application a kernel older than the current Long Term Supported kernel (3.16). If you are an unsupported kernel, you put yourself at risk of the next big security attack. If you are selling a product, then using older kernels is just asking it to be pawned.