automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: |WARNING| pw153563 [PATCH v1 2/4] ring/soring: fix head-tail synchronization issue
Date: Wed, 21 May 2025 13:15:58 +0200 (CEST)	[thread overview]
Message-ID: <20250521111558.29CB0123FAA@dpdk.org> (raw)
In-Reply-To: <20250521111432.207936-3-konstantin.ananyev@huawei.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153563

_coding style issues_


WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#34: 
Subject: [PATCH v1 2/4] ring/soring: fix head-tail synchronization issue

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#57: 
While running soring_stress_autotest on machine with Ampere Altra Max CPU,

WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#61: 
test_worker_prcs:_st_ring_dequeue_bulk: check_updt_elem(lc=11, num=42) failed at 11-th iter, offending object: 0x103df1480

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#63: 
EAL: PANIC in soring_verify_state():

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#64: 
line:382 from:acquire_state_update: soring=0x103c72c00, stage=0, idx=0x7fb8, expected={.stnum=0, .ftoken=0}, actual={.stnum=0x80000028, .ftoken=0x47fb8};

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#82: 
do { …; success=(CAS(&head); } while(success==0);

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#83: 
loop, i.e. – only when first CAS(&cons.head) attempt fails.

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#86: 
1) soring_dequeue() calls _fianlize()

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#90: 
2) soring_dequeue() calls move_cons_head() again.

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#93: 
3) soring_dequeue() is called on different thread

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#97: 
     Then CAS(cons.head) fails and returns a new value for it,

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#109: 
for CAS operation.

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#110: 
While in rte_ring_c11_pvt.h – CAS operation is invoked with relaxed

WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#113: 
To fix that issue for SORING - I introduced an extra release fence straight

WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#124: 
for CAS(&head) operation in move_head().

WARNING:TYPO_SPELLING: 'couterpart' may be misspelled - perhaps 'counterpart'?
#126: 
couterpart 'tail' latest value will also become visible.

total: 0 errors, 16 warnings, 17 lines checked

           reply	other threads:[~2025-05-21 11:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250521111432.207936-3-konstantin.ananyev@huawei.com>]

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=20250521111558.29CB0123FAA@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=konstantin.ananyev@huawei.com \
    --cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).