From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/3] kni: remove single mempool, single mem_chunk restriction
Date: Wed, 21 Sep 2016 19:20:06 +0200 [thread overview]
Message-ID: <1780631.bJrZJTOcPN@xps13> (raw)
In-Reply-To: <1472124636-27227-1-git-send-email-ferruh.yigit@intel.com>
2016-08-25 12:30, Ferruh Yigit:
> Use mempool buf_addr and buf_physaddr fields for address translation.
>
> Since each mbuf address calculated separately, the restriction of all
> mbufs should come from a continuous memory restriction is no more valid.
>
> mbuf related FIFO's content changed, rx_q and alloc_q now carries
> physical address of mbufs. tx_q and free_q content not changed, they
> still carries virtual address of mbufs.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
The next 2 patches have been squashed with the first one as they are
tightly related.
prev parent reply other threads:[~2016-09-21 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 11:30 Ferruh Yigit
2016-08-25 11:30 ` [dpdk-dev] [PATCH 2/3] kni: don't use mbuf_va and mbuf_kva Ferruh Yigit
2016-08-25 11:30 ` [dpdk-dev] [PATCH 3/3] kni: remove mempool number of mem chunk check Ferruh Yigit
2016-09-21 17:20 ` Thomas Monjalon [this message]
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=1780631.bJrZJTOcPN@xps13 \
--to=thomas.monjalon@6wind.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).