DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ajeet Gill (ajgill)" <ajgill@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] kni: remove single mempool, single mem_chunk restriction
Date: Tue, 26 Sep 2017 00:51:33 +0000	[thread overview]
Message-ID: <73D9C2C2-7419-48C2-BEAA-79AEDE85A96D@cisco.com> (raw)

Hello Ferruh,
 I see there might be issue with multi-chunk mempools in the KNI kernel driver.
It looks like the logic of calculating the addresses is as following the below method:

Va-Pa=Vb-Pb.

where V’s are the Virtual addresses and P’s are the physical addresses.
But this formula may not be true for multi-chunk mempools.

I have seen kernel crashes when trying to access the multi-segmented buffers on KNI interface.
I have a working patch for the issue.
I will submit it for review.

Thanks
Ajeet



             reply	other threads:[~2017-09-26  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26  0:51 Ajeet Gill (ajgill) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-10 10:47 Ferruh Yigit

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=73D9C2C2-7419-48C2-BEAA-79AEDE85A96D@cisco.com \
    --to=ajgill@cisco.com \
    --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 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).