From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <clearasu@gmail.com>
Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com
 [209.85.217.177]) by dpdk.org (Postfix) with ESMTP id ADE1737B4
 for <dev@dpdk.org>; Mon, 28 Mar 2016 22:24:10 +0200 (CEST)
Received: by mail-lb0-f177.google.com with SMTP id vo2so35931643lbb.1
 for <dev@dpdk.org>; Mon, 28 Mar 2016 13:24:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to;
 bh=FZusKGzFnMteqzv15j1XPvW9bCUG/9+HVjZu+yP8XNQ=;
 b=ZQvR3sezO72qafiB92d6Jdft4/0C1EjBrvcpCDRDChlYbkDhQqdHkJIj369aaYp6MP
 gtbiCY9/KYieJjRECKw38xkVbytkRQZDGrFqllF2AXuoabVcAw2RCo7UhzRMMN0uCMg0
 jQDWzoPGP1UzUw4K2G2nPR2KcrLLuoMTkShSpfXvLE1xDOlootid0mo3+sq7vsx/tqDY
 iLMVGplnKejvehNsY68p+k3N4icmxlWHiYsrPWeIQobeaYOC1y1vyj4DITXCo2nGDTDY
 OFe3L8G4amBiVg5odyFiJdOF+ARFEjQMLUWTBiHMM1hapJJDACTcym0pf+FSmuAenZEe
 WHDw==
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;
 bh=FZusKGzFnMteqzv15j1XPvW9bCUG/9+HVjZu+yP8XNQ=;
 b=e8QUfgEHhfpoM5xvsybroWP24xgM0Re/kRtNZRcwVXoD00ZrCOADn6CiKQk9E2Uord
 2a3ZLbvC/ZBImB+x2ljW98j+DEMescAa4eQiS0b2IFRNLXqe48mOAMClhx9WUxUXjnUO
 Wvyx0Wt7GAMJMXennfsVqxnWa9sbaAQOn8nSHwYBdWK2PGwzcW3xFfUz/BqyAlteKIGQ
 ExSjcnWgo+Zh3gVeN8ecUYeb+VoObbOy5jdBhYX7aBSnc2cHp4dpZWicFWQTod45wcX/
 iHm6BLbzXU1b6p73bWS3KNI41FQXWdnuGcUM7KpvEqNudawLpes/dBqHemVx6vty2rrL
 D0+w==
X-Gm-Message-State: AD7BkJJ1/cM8ayCUH1kOJ7IiIh12KJOLcUk2n0nl15WPadXeuPwfLOhCq8eDYEtLKoEhWXqC6O1aIDbC3GqXMw==
MIME-Version: 1.0
X-Received: by 10.112.97.162 with SMTP id eb2mr10812764lbb.132.1459196650275; 
 Mon, 28 Mar 2016 13:24:10 -0700 (PDT)
Received: by 10.114.233.36 with HTTP; Mon, 28 Mar 2016 13:24:10 -0700 (PDT)
Date: Mon, 28 Mar 2016 13:24:10 -0700
Message-ID: <CAKj5Mju2SuQFGAtmq_RX1sQCSVGbFq2EfS58TpHn4BZym6_d1w@mail.gmail.com>
From: Clarylin L <clearasu@gmail.com>
To: dev@dpdk.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev]  is ixgbe supporting multi-segment mbuf?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2016 20:24:10 -0000

ixgbe_recv_scattered_pkts was set to be the rx function. Receiving packets
smaller than mbuf size works perfectly. However, if an incoming packet is
greater than the maximum acceptable length of one =E2=80=9Cmbuf=E2=80=9D da=
ta size,
receiving does not work. In this case, isn't it supposed to use
mbuf chaining to receive?

The port has both jumbo_frame and enable_scatter being on. are these two
flags good enough to make mbuf chaining going?