From: Alex Wang <alex@awakenetworks.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Alex Wang <ee07b291@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2 v3] kni: add documentation for the mempool capacity
Date: Thu, 9 Jun 2016 10:06:59 -0700 [thread overview]
Message-ID: <CAFg=G3PiXkf_QyQM643KqhC21HHTbUUJUK=0c+_+6bV8D_rMvQ@mail.gmail.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20257E513@IRSMSX103.ger.corp.intel.com>
Just to confirm, should I do anything before it gets merged?
On Thu, Jun 9, 2016 at 5:03 AM, Mcnamara, John <john.mcnamara@intel.com>
wrote:
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Wang
> > Sent: Saturday, May 21, 2016 8:59 AM
> > To: dev@dpdk.org
> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Alex Wang
> > <alex@awakenetworks.com>
> > Subject: [dpdk-dev] [PATCH 2/2 v3] kni: add documentation for the mempool
> > capacity
> >
> > From: Alex Wang <alex@awakenetworks.com>
> >
> > Function like 'rte_kni_rx_burst()' keeps allocating 'MAX_MBUF_BURST_NUM'
> > mbufs to kni fifo queue unless the queue's capacity
> > ('KNI_FIFO_COUNT_MAX') is reached. So, if the mempool is under-
> > provisioned, user may run into "Out of Memory" logs from KNI code.
> > This commit documents the need to provision mempool capacity of more than
> > "2 x KNI_FIFO_COUNT_MAX" for each KNI interface.
> >
> > Signed-off-by: Alex Wang <alex@awakenetworks.com>
> > Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
>
>
next prev parent reply other threads:[~2016-06-09 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 7:58 [dpdk-dev] [PATCH 1/2 v3] kni: fix inverted function comments Alex Wang
2016-05-21 7:58 ` [dpdk-dev] [PATCH 2/2 v3] kni: add documentation for the mempool capacity Alex Wang
2016-06-09 12:03 ` Mcnamara, John
2016-06-09 17:06 ` Alex Wang [this message]
2016-06-09 17:10 ` Mcnamara, John
2016-06-14 15:16 ` Thomas Monjalon
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='CAFg=G3PiXkf_QyQM643KqhC21HHTbUUJUK=0c+_+6bV8D_rMvQ@mail.gmail.com' \
--to=alex@awakenetworks.com \
--cc=dev@dpdk.org \
--cc=ee07b291@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@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).