From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shrikrishna Khare <skhare@shri-linux.eng.vmware.com>,
Chas Williams <3chas3@gmail.com>
Cc: dev@dpdk.org, skhare@vmware.com,
"Charles (Chas) Williams" <ciwillia@mail.eng.vyatta.net>,
Chas Williams <chas3@att.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/vmxnet3: set the queue shared buffer at start
Date: Tue, 13 Mar 2018 15:20:20 +0000 [thread overview]
Message-ID: <36c5dbe5-9ae3-a1c6-50a3-9d45afd39e35@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1803121045320.23969@shri-linux.eng.vmware.com>
On 3/12/2018 5:45 PM, Shrikrishna Khare wrote:
>
>
> On Wed, 17 Jan 2018, Chas Williams wrote:
>
>> From: "Charles (Chas) Williams" <ciwillia@mail.eng.vyatta.net>
>>
>> If a reconfiguration happens, queuedesc is reallocated. Any queues that
>> are preserved point to the previous queuedesc since the queues are only
>> configured during queue setup. Delay configuration of the shared queue
>> pointers until device start when queuedesc is no longer changing.
>>
>> Fixes: 8618d19b52b1 ("net/vmxnet3: reallocate shared memzone on re-config")
>>
>> Signed-off-by: Chas Williams <chas3@att.com>
>
> Acked-by: Shrikrishna Khare <skhare@vmware.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-03-13 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 15:04 Chas Williams
2018-01-17 15:04 ` [dpdk-dev] [PATCH 2/2] net/vmxnet3: keep consistent link status Chas Williams
2018-03-12 17:45 ` [dpdk-dev] [PATCH 1/2] net/vmxnet3: set the queue shared buffer at start Shrikrishna Khare
2018-03-13 15:20 ` 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=36c5dbe5-9ae3-a1c6-50a3-9d45afd39e35@intel.com \
--to=ferruh.yigit@intel.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=ciwillia@mail.eng.vyatta.net \
--cc=dev@dpdk.org \
--cc=skhare@shri-linux.eng.vmware.com \
--cc=skhare@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).