DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Mussar, Gary" <gmussar@ciena.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_kni.ko with lo_mode=lo_mode_ring
Date: Fri, 2 Sep 2016 14:16:01 +0000	[thread overview]
Message-ID: <C1D08A83-2819-49E4-9ACE-682E3AF2408F@intel.com> (raw)
In-Reply-To: <C281A17C31CFD745B242416D0E96EC63ABA5E06C@ONWVEXCHMB04.ciena.com>

HI Gary,

Regards,
Keith

> On Sep 2, 2016, at 8:39 AM, Mussar, Gary <gmussar@ciena.com> wrote:
> 
> The pktgen docs state that the rte_kni.ko should be loaded with lo_mode=lo_mode_ring however the source in dpdk master does not appear to understand this value. This wasn't an issue in the past since the kni code would simply disable lo_mode if you passed in an unknown value.
> 
> The Ubuntu 4.4.0-36-generic kernel no longer loads the module if the passed value is not in the table of known values (the 4.4.0-34-generic kernel would still load the module).
> 
> I have 2 questions:
> 1)
> Why does pktgen specify using a value for lo_mode that the source does not support? Is lo_mode_ring something that is coming but not yet submitted?

The KNI support and kernel module is more of a DPDK issue then Pktgen, which is the application on top of DPDK. I do not know the reason lo_mode_ring is not working correctly. Look in the Maintainers file and see who maintains the KNI code.

> 
> 2)
> Is the Ubuntu kernel being over aggressive in parameter checking or is this a "good" thing? If it is good, then should the pktgen docs be indicating that an unsupported value be used for lo_mode?

I assume the Ubuntu Kernel is attempting to protect itself. Each time the kernel is updated it is a good think to recompile DPDK and the KNI kernel module or the module may not load because of a version mis-match.

> 
> Gary

  reply	other threads:[~2016-09-02 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 13:39 [dpdk-dev] [PKTGEN] " Mussar, Gary
2016-09-02 14:16 ` Wiles, Keith [this message]
2016-09-02 14:55   ` [dpdk-dev] " Ferruh Yigit
2016-09-02 15:54     ` Mussar, Gary

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=C1D08A83-2819-49E4-9ACE-682E3AF2408F@intel.com \
    --to=keith.wiles@intel.com \
    --cc=dev@dpdk.org \
    --cc=gmussar@ciena.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).