From: "Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)" <jgrajcia@cisco.com>
To: "Yigit, Ferruh" <ferruh.yigit@linux.intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [RFC v3] net/memif: allow for full key size in socket name
Date: Mon, 7 Oct 2019 09:01:10 +0000 [thread overview]
Message-ID: <75c2d0a4d0d140bab4c8caca08c7a1da@XCH-ALN-004.cisco.com> (raw)
In-Reply-To: <f3ce918e-3624-79d5-9e96-e5cb9510b03d@linux.intel.com>
Hi Ferruh,
> Hi Jakub,
>
> While testing your zero-copy patch [1], I stuck to a bind() error [2].
> When provided a socket length bigger than "sizeof(struct sockaddr)", bind()
> fails. I am testing this on a Fedora system.
> I wonder if there is a check in glibc related to the length.
Zero-copy patch does not contain this fix, in fact, I can't find this patch in the commit log.
It was supposed to be applied on 2019-09-13.
http://git.dpdk.org/next/dpdk-next-net/log/?ofs=400
Was there any problem with apply? Maybe because the patch is RFC?
>
> What was your test platform for the change?
Ubuntu 18.04
>
>
>
> [1]
> https://patches.dpdk.org/patch/57817/
>
> [2]
> memif_socket_create(): NULL: Failed to setup socket /run/memif.sock: Invalid
> argument
next prev parent reply other threads:[~2019-10-07 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 16:06 [dpdk-dev] [RFC] net/memif: allow for full key size in socket name Stephen Hemminger
2019-07-16 17:18 ` [dpdk-dev] [RFC v2] " Stephen Hemminger
2019-07-16 17:20 ` [dpdk-dev] [RFC v3] " Stephen Hemminger
2019-08-30 7:17 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)
2019-09-13 18:47 ` Ferruh Yigit
2019-10-04 12:41 ` Yigit, Ferruh
2019-10-07 9:01 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco) [this message]
2019-10-07 15:21 ` Ferruh Yigit
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=75c2d0a4d0d140bab4c8caca08c7a1da@XCH-ALN-004.cisco.com \
--to=jgrajcia@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@linux.intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=stephen@networkplumber.org \
/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).