From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Tal Shnaiderman <talshn@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
"navasile@linux.microsoft.com" <navasile@linux.microsoft.com>,
"ranjit.menon@intel.com" <ranjit.menon@intel.com>,
"harini.ramakrishnan@microsoft.com"
<harini.ramakrishnan@microsoft.com>,
"ocardona@microsoft.com" <ocardona@microsoft.com>,
"Dmitry Malloy (MESHCHANINOV)" <dmitrym@microsoft.com>,
Yohad Tor <yohadt@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_mbuf structure size in Windows
Date: Wed, 13 May 2020 12:34:17 +0300 [thread overview]
Message-ID: <20200513123417.618020c8@sovereign> (raw)
In-Reply-To: <AM0PR05MB53138DF1AD8D1A202FF5C87DA9BF0@AM0PR05MB5313.eurprd05.prod.outlook.com>
On Wed, 13 May 2020 08:55:11 +0000
Tal Shnaiderman <talshn@mellanox.com> wrote:
> Thank you Dmitry, do we plan to push this WO or stay with 3 cache
> lines uniformly on Windows builds until the clang bug is resolved?
> (I'm out of the loop regarding this issue).
Let's bring this to the today's call. IMO, uniform layout would allow
building DPDK with MinGW and apps with Clang, which is good, and
performance is not a current priority, butI may be missing something.
--
Dmitry Kozlyuk
prev parent reply other threads:[~2020-05-13 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 7:55 Tal Shnaiderman
2020-05-13 8:04 ` Omar Cardona
2020-05-13 8:07 ` Omar Cardona
2020-05-13 8:50 ` Tal Shnaiderman
2020-05-13 8:35 ` Dmitry Kozlyuk
2020-05-13 8:55 ` Tal Shnaiderman
2020-05-13 9:34 ` Dmitry Kozlyuk [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=20200513123417.618020c8@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yohadt@mellanox.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).