From: cys <chaoys155@163.com>
To: dev <dev@dpdk.org>, "ferruh.yigit" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] kni: continuous memory restriction ?
Date: Fri, 9 Mar 2018 20:14:20 +0800 (CST) [thread overview]
Message-ID: <528c4b67.fc.1620aaef223.Coremail.chaoys155@163.com> (raw)
Commit 8451269e6d7ba7501723fe2efd0 said "remove continuous memory restriction";
http://dpdk.org/browse/dpdk/commit/lib/librte_eal/linuxapp/kni/kni_net.c?id=8451269e6d7ba7501723fe2efd05745010295bac
For chained mbufs(nb_segs > 1), function va2pa use the offset of previous mbuf to calculate physical address of next mbuf.
So anywhere guarante that all mbufs have the same offset (buf_addr - buf_physaddr) ?
Or have I misunderstood chained mbufs?
next reply other threads:[~2018-03-09 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 12:14 cys [this message]
2018-03-13 9:36 ` cys
2018-03-13 14:57 ` Ferruh Yigit
2018-03-14 0:35 ` cys
2018-03-20 15:25 ` 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=528c4b67.fc.1620aaef223.Coremail.chaoys155@163.com \
--to=chaoys155@163.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).