From: Tal Shnaiderman <talshn@mellanox.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.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 08:55:11 +0000 [thread overview]
Message-ID: <AM0PR05MB53138DF1AD8D1A202FF5C87DA9BF0@AM0PR05MB5313.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200513113539.226b1a58@sovereign>
> Subject: Re: rte_mbuf structure size in Windows
>
> Hi,
>
> This is the issue we were talking about from the beginning of year. Microsoft
> was supposed to track the bug and allocate resources to fix it if possible. On
> the last community call, Naty and Omar claimed there is no noticeable
> performance impact with l2fwd if mbuf spans 3 cache lines, but DmitryM
> commented this may depend on cache utilization.
>
> For GCC, the following workaround exists:
>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
> 2Fgithub.com%2FPlushBeaver%2Fdpdk%2Fcommit%2F37f052cb18d1d5d4258
> 18196d5e1d15a7ada0de0&data=02%7C01%7Ctalshn%40mellanox.com%
> 7Ca5df987ffdff439a4ea608d7f7189f62%7Ca652971c7d2e4d9ba6a4d149256f46
> 1b%7C0%7C0%7C637249557444653368&sdata=dkaDS7%2FM%2BvOwgx
> RVjfRsGkAO66rGhRCAHUHzybpOxYY%3D&reserved=0
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).
>
> No workaround for Clang is known, bug URL:
>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
> 2Fbugs.llvm.org%2Fshow_bug.cgi%3Fid%3D24383&data=02%7C01%7Ct
> alshn%40mellanox.com%7Ca5df987ffdff439a4ea608d7f7189f62%7Ca652971c
> 7d2e4d9ba6a4d149256f461b%7C0%7C0%7C637249557444653368&sdata
> =XJnc7Q%2BTRt%2F2TyPEOl3uO2cXhdCFzArbvreDak65DJw%3D&reserv
> ed=0
>
> --
> Dmitry Kozlyuk
next prev parent reply other threads:[~2020-05-13 8:55 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 [this message]
2020-05-13 9:34 ` Dmitry Kozlyuk
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=AM0PR05MB53138DF1AD8D1A202FF5C87DA9BF0@AM0PR05MB5313.eurprd05.prod.outlook.com \
--to=talshn@mellanox.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--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=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).