From: Jiri Pirko <jiri@resnulli.us>
To: Yinjun Zhang <yinjun.zhang@corigine.com>
Cc: Louis Peens <louis.peens@corigine.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Fei Qin <fei.qin@nephogine.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
oss-drivers <oss-drivers@corigine.com>
Subject: Re: [PATCH net-next 2/2] nfp: customize the dim profiles
Date: Thu, 1 Feb 2024 08:42:57 +0100 [thread overview]
Message-ID: <ZbtLgcBcd5B2ZkPC@nanopsycho> (raw)
In-Reply-To: <DM6PR13MB37051F13B28B53F2CE135CE0FC432@DM6PR13MB3705.namprd13.prod.outlook.com>
Thu, Feb 01, 2024 at 03:16:50AM CET, yinjun.zhang@corigine.com wrote:
>On Wednesday, January 31, 2024 5:39 PM, Jiri Pirko wrote:
><...>
>> It looks incorrect to hardcode it like this. There is a reason this is
>> abstracted out in lib/dim/net_dim.c to avoid exactly this. Can't you
>> perhaps introduce your modified profile there and keep using
>> net_dim_get_[tr]x_moderation() helpers?
>>
>
>We don't know if this introduced profile is adaptable to other NICs/vendors,
>it's generated based on NFP's performance. Do you really think it's
>appropriate to move it to the net_dim.c as a new common profile like:
>enum dim_cq_period_mode {
> DIM_CQ_PERIOD_MODE_START_FROM_EQE = 0x0,
> DIM_CQ_PERIOD_MODE_START_FROM_CQE = 0x1,
>+ DIM_CQ_PERIOD_MODE_SPECIFIC_0 = 0x2,
Maybe. Can't think of anything better atm. Maybe others would have some
ideas.
> DIM_CQ_PERIOD_NUM_MODES
> };
>
>
prev parent reply other threads:[~2024-02-01 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 8:54 [PATCH net-next 0/2] nfp: series of minor driver improvements Louis Peens
2024-01-31 8:54 ` [PATCH net-next 1/2] nfp: update devlink device info output Louis Peens
2024-01-31 9:31 ` Jiri Pirko
2024-01-31 9:40 ` Louis Peens
2024-02-02 4:29 ` Jakub Kicinski
2024-01-31 8:54 ` [PATCH net-next 2/2] nfp: customize the dim profiles Louis Peens
2024-01-31 9:39 ` Jiri Pirko
2024-01-31 11:25 ` Louis Peens
2024-02-01 2:16 ` Yinjun Zhang
2024-02-01 7:42 ` Jiri Pirko [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=ZbtLgcBcd5B2ZkPC@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=fei.qin@nephogine.com \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=yinjun.zhang@corigine.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).