From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jan Blunck <jblunck@infradead.org>,
"Charles (Chas) Williams" <ciwillia@brocade.com>
Cc: dev <dev@dpdk.org>, yongwang@vmware.com
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: fix queue size changes
Date: Thu, 16 Mar 2017 11:38:13 +0000 [thread overview]
Message-ID: <f8b66470-6963-81ff-d578-148bd583d6a7@intel.com> (raw)
In-Reply-To: <CALe+Z00i3Tq4MBN5rZuXqexppPuY9FbUKWxURfQnhZkseXxmtQ@mail.gmail.com>
On 3/15/2017 6:19 PM, Jan Blunck wrote:
> On Wed, Mar 15, 2017 at 1:35 PM, Charles (Chas) Williams
> <ciwillia@brocade.com> wrote:
>> If the user reconfigures the queue size, then the previously allocated
>> memzone may potentially be too small. Release the memzone when a queue
>> is released and allocate a new one each time a queue is setup.
>>
>> While here convert to rte_eth_dma_zone_reserve() which does basically
>> the same things as the private function.
>>
>> Fixes: dfaff37fc46d ("vmxnet3: import new vmxnet3 poll mode driver implementation")
Cc: stable@dpdk.org
>>
>> Signed-off-by: Chas Williams <ciwillia@brocade.com>
> Acked-by: Jan Blunck <jblunck@infradead.org>
Acked-by: Shrikrishna Khare <skhare@vmware.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-03-16 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 22:41 Charles (Chas) Williams
2017-03-14 16:11 ` Jan Blunck
2017-03-14 16:38 ` Charles (Chas) Williams
2017-03-15 8:18 ` Jan Blunck
2017-03-15 9:45 ` Charles (Chas) Williams
2017-03-15 10:05 ` Jan Blunck
2017-03-15 10:06 ` Charles (Chas) Williams
2017-03-15 12:34 ` Charles (Chas) Williams
2017-03-15 12:35 ` Charles (Chas) Williams
2017-03-15 17:57 ` Yong Wang
2017-03-15 18:30 ` Shrikrishna Khare
2017-03-15 18:19 ` Jan Blunck
2017-03-16 11:38 ` Ferruh Yigit [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=f8b66470-6963-81ff-d578-148bd583d6a7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ciwillia@brocade.com \
--cc=dev@dpdk.org \
--cc=jblunck@infradead.org \
--cc=yongwang@vmware.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).