From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>
Subject: Re: [PATCH 0/8] optimize the firmware loading process
Date: Tue, 23 Jan 2024 09:14:14 +0000 [thread overview]
Message-ID: <009856cb-bfef-437f-a62c-98c2c617f61f@amd.com> (raw)
In-Reply-To: <SJ0PR13MB554576080831FF2F385BB1009E742@SJ0PR13MB5545.namprd13.prod.outlook.com>
On 1/23/2024 1:46 AM, Chaoyong He wrote:
>
>
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yigit@amd.com>
>> Sent: Monday, January 22, 2024 11:09 PM
>> To: Chaoyong He <chaoyong.he@corigine.com>; dev@dpdk.org
>> Cc: oss-drivers <oss-drivers@corigine.com>
>> Subject: Re: [PATCH 0/8] optimize the firmware loading process
>>
>> On 1/15/2024 2:54 AM, Chaoyong He wrote:
>>> This patch series aims to speedup the DPDK application start by
>>> optimize the firmware loading process in sereval places.
>>> We also simplify the port name in multiple PF firmware case to make
>>> the customer happy.
>>>
>>
>> <...>
>>
>>> net/nfp: add the elf module
>>> net/nfp: reload the firmware only when firmware changed
>>
>> Above commit adds elf parser capability and second one loads firmware when
>> build time is different.
>>
>> I can see this is an optimization effort, to understand FW status before loading
>> FW, but relying on build time seems fragile. Does it help to add a new section
>> to store version information and evaluate based on this information?
>>
>
> We have a branch of firmware (several app type combined with NFD3/NFDk) with the same version information(monthly publish),
> so the version information can't help us, because we can't distinguish among them.
>
> But the build time is different for every firmware, and that's the reason we choose it.
>
If version is same although FW itself is different, isn't this problem
on its own? Perhaps an additional field is required in version syntax.
next prev parent reply other threads:[~2024-01-23 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 2:54 Chaoyong He
2024-01-15 2:54 ` [PATCH 1/8] net/nfp: add the interface for getting the firmware name Chaoyong He
2024-01-15 2:54 ` [PATCH 2/8] net/nfp: speed up the firmware loading process Chaoyong He
2024-01-15 2:54 ` [PATCH 3/8] net/nfp: optimize loading the firmware process Chaoyong He
2024-01-15 2:54 ` [PATCH 4/8] net/nfp: enlarge the range of skipping loading the firmware Chaoyong He
2024-01-15 2:54 ` [PATCH 5/8] net/nfp: add the step of clearing the beat time Chaoyong He
2024-01-15 2:54 ` [PATCH 6/8] net/nfp: add the elf module Chaoyong He
2024-01-15 2:54 ` [PATCH 7/8] net/nfp: reload the firmware only when firmware changed Chaoyong He
2024-01-15 2:54 ` [PATCH 8/8] net/nfp: simplify the port name for multiple PFs Chaoyong He
2024-01-22 15:08 ` [PATCH 0/8] optimize the firmware loading process Ferruh Yigit
2024-01-23 1:46 ` Chaoyong He
2024-01-23 9:14 ` Ferruh Yigit [this message]
2024-01-23 11:27 ` Chaoyong He
2024-01-23 11:42 ` Ferruh Yigit
2024-01-26 8:25 ` Chaoyong He
2024-01-23 15:18 ` Ferruh Yigit
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=009856cb-bfef-437f-a62c-98c2c617f61f@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=oss-drivers@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).