From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "You, KaisenX" <kaisenx.you@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: [PATCH] net/iavf:fix slow memory allocation
Date: Thu, 8 Dec 2022 08:46:36 +0000 [thread overview]
Message-ID: <MW3PR11MB45879A0655E66DC35E27DF2AE31D9@MW3PR11MB4587.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221117065726.277672-1-kaisenx.you@intel.com>
> -----Original Message-----
> From: You, KaisenX <kaisenx.you@intel.com>
> Sent: Thursday, November 17, 2022 2:57 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Yang, Qiming <qiming.yang@intel.com>; Zhou, YidingX
> <yidingx.zhou@intel.com>; You, KaisenX <kaisenx.you@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Subject: [PATCH] net/iavf:fix slow memory allocation
>
> In some cases, the DPDK does not allocate hugepage heap memory to
> some sockets due to the user setting parameters
> (e.g. -l 40-79, SOCKET 0 has no memory).
> When the interrupt thread runs on the corresponding core of this
> socket, each allocation/release will execute a whole set of heap
> allocation/release operations,resulting in poor performance.
> Instead we call malloc() to get memory from the system's
> heap space to fix this problem.
>
> Fixes: cb5c1b91f76f ("net/iavf: add thread for event callbacks")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kaisen You <kaisenx.you@intel.com>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
next prev parent reply other threads:[~2022-12-08 8:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 6:57 Kaisen You
2022-11-18 8:22 ` Jiale, SongX
2022-12-07 9:07 ` You, KaisenX
2022-12-08 8:46 ` Wu, Jingjing [this message]
2022-12-08 15:04 ` Ferruh Yigit
2022-12-13 7:52 ` You, KaisenX
2022-12-13 9:35 ` Ferruh Yigit
2022-12-13 13:27 ` Ferruh Yigit
2022-12-20 6:52 ` You, KaisenX
2022-12-20 9:33 ` David Marchand
2022-12-20 10:11 ` You, KaisenX
2022-12-20 10:33 ` David Marchand
2022-12-21 9:12 ` You, KaisenX
2022-12-21 10:50 ` David Marchand
2022-12-22 6:42 ` You, KaisenX
2022-12-27 6:06 ` You, KaisenX
2023-01-10 10:16 ` David Marchand
2023-01-13 6:24 ` You, KaisenX
2022-12-21 13:48 ` Ferruh Yigit
2022-12-22 7:23 ` You, KaisenX
2022-12-22 12:06 ` Ferruh Yigit
2022-12-26 2:17 ` Zhang, Qi Z
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=MW3PR11MB45879A0655E66DC35E27DF2AE31D9@MW3PR11MB4587.namprd11.prod.outlook.com \
--to=jingjing.wu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=kaisenx.you@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=yidingx.zhou@intel.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).