mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Changwoo Min <changwoo@igalia.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: lukasz.luba@arm.com, rafael@kernel.org, len.brown@intel.com,
	pavel@kernel.org, christian.loehle@arm.com, tj@kernel.org,
	kernel-dev@igalia.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 04/11] PM: EM: Add the infrastructure for command processing.
Date: Wed, 4 Jun 2025 18:11:02 +0200	[thread overview]
Message-ID: <be23f55c-329c-444d-b5d8-83ae29b05387@igalia.com> (raw)
In-Reply-To: <aD4CrOmIwhUI-pet@wunner.de>



On 6/2/25 04:59, Lukas Wunner wrote:
> On Thu, May 29, 2025 at 09:13:08AM +0900, Changwoo Min wrote:
>> +static int em_genl_cmd_doit(struct sk_buff *skb, struct genl_info *info)
>> +{
>> +	struct param p = { .attrs = info->attrs };
>> +	struct sk_buff *msg;
>> +	void *hdr;
>> +	int cmd = info->genlhdr->cmd;
>> +	int ret = -EMSGSIZE;
>> +
>> +	msg = genlmsg_new(NLMSG_GOODSIZE, GFP_KERNEL);
>> +	if (!msg)
>> +		return -ENOMEM;
> 
> Just a heads-up, I know everyone recommends NLMSG_GOODSIZE but in reality
> it's not that great because netlink_trim() reallocates the skb and copies
> the entire linear buffer if it determines that the skb is half-empty.
> Performance suffers as a result.  So it's actually better to calculate
> the exact message length prior to allocation.
Thank you, Lukas, for sharing the experience. I will address it in the
next version.

Regards,
Changwoo Min

  reply	other threads:[~2025-06-04 16:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29  0:13 [PATCH 00/11] PM: EM: Add netlink support for the energy model Changwoo Min
2025-05-29  0:13 ` [PATCH 01/11] PM: EM: Add ENERGY_MODEL_NETLINK Kconfig Changwoo Min
2025-05-29  0:13 ` [PATCH 02/11] PM: EM: Add a skeleton code for netlink notification Changwoo Min
2025-06-02 19:53   ` Lukas Wunner
2025-06-03  6:01     ` Changwoo Min
2025-05-29  0:13 ` [PATCH 03/11] PM: EM: Initialize the netlink notification during booting Changwoo Min
2025-05-29  0:13 ` [PATCH 04/11] PM: EM: Add the infrastructure for command processing Changwoo Min
2025-06-02 19:59   ` Lukas Wunner
2025-06-04 16:11     ` Changwoo Min [this message]
2025-05-29  0:13 ` [PATCH 05/11] PM: EM: Assign a unique ID when creating a performance domain Changwoo Min
2025-05-29  0:13 ` [PATCH 06/11] PM: EM: Expose the ID of a performance domain via debugfs Changwoo Min
2025-05-29  0:13 ` [PATCH 07/11] PM: EM: Add an iterator and accessor for the performance domain Changwoo Min
2025-05-29  0:13 ` [PATCH 08/11] PM: EM: Implement EM_GENL_CMD_PD_GET_ID Changwoo Min
2025-05-29  0:13 ` [PATCH 09/11] PM: EM: Implement EM_GENL_CMD_PD_GET_TBL Changwoo Min
2025-05-29  0:13 ` [PATCH 10/11] PM: EM: Implement event notification Changwoo Min
2025-05-29  0:13 ` [PATCH 11/11] PM: EM: Notify an event when the performance domain changes Changwoo Min
2025-06-02 11:52 ` [PATCH 00/11] PM: EM: Add netlink support for the energy model Lukasz Luba

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=be23f55c-329c-444d-b5d8-83ae29b05387@igalia.com \
    --to=changwoo@igalia.com \
    --cc=christian.loehle@arm.com \
    --cc=kernel-dev@igalia.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=lukasz.luba@arm.com \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®