All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 164] configure rx queue for JUMBO frame returns warning as offload is 0x0, but eth_pcap_rx_jumbo is present
Date: Tue, 11 Dec 2018 16:21:26 +0000	[thread overview]
Message-ID: <bug-164-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=164

            Bug ID: 164
           Summary: configure rx queue for JUMBO frame returns warning as
                    offload is 0x0, but eth_pcap_rx_jumbo is present
           Product: DPDK
           Version: 18.11
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: vipin.varghese@intel.com
  Target Milestone: ---

DPDK version: 18.05 and 18.11 - error seen
Documentation: http://doc.dpdk.org/guides/nics/overview.html - states JUMBO is
supported
driver/net/rte_eth_pcap.c: function eth_pcap_rx_jumbo - supported

Question: Why is offload flag not supported but supporting by function in DPDK
18.05 and 18.11?

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-12-11 16:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-164-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.