From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)"
<jgrajcia@cisco.com>, "Július Milan" <jmilan.dev@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/memif: fix init handling when already connected
Date: Mon, 9 Mar 2020 14:44:14 +0000 [thread overview]
Message-ID: <69459402-893d-f4a7-d0e8-44780d226565@intel.com> (raw)
In-Reply-To: <DM6PR11MB4186D691EE48FE1F2378B998DF100@DM6PR11MB4186.namprd11.prod.outlook.com>
On 2/19/2020 1:06 PM, Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)
wrote:
>> -----Original Message-----
>> From: Július Milan <jmilan.dev@gmail.com>
>> Sent: Wednesday, February 19, 2020 9:19 AM
>> To: dev@dpdk.org; Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)
>> <jgrajcia@cisco.com>
>> Subject: [dpdk-dev][PATCH 2/2] net/memif: fix init handling when already
>> connected
>>
>> This patch fixes the situation when there is already connected pair of memif
>> interfaces and another slave tries to initiate the connection with (already
>> occupied) master. Expected behavior is that the second slave is refused and
>> gets disconnect message with reason: "Already connected", while old
>> connection remains functional.
>>
>> Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD")
>>
>> Signed-off-by: Július Milan <jmilan.dev@gmail.com>
>
> Reviewed-by: Jakub Grajciar <jgrajcia@cisco.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-03-09 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 8:19 Július Milan
2020-02-19 13:06 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)
2020-03-09 14:44 ` 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=69459402-893d-f4a7-d0e8-44780d226565@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=jmilan.dev@gmail.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).