target-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.com>
To: Mike Christie <michael.christie@oracle.com>,
	mlombard@redhat.com, martin.petersen@oracle.com,
	d.bogdanov@yadro.com, bvanassche@acm.org,
	linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] scsi: target: Move LUN stats to per CPU
Date: Thu, 18 Sep 2025 08:31:52 +0200	[thread overview]
Message-ID: <03e53a96-d94e-4608-b52e-bbd87b8a90af@suse.com> (raw)
In-Reply-To: <20250917221338.14813-4-michael.christie@oracle.com>

On 9/18/25 00:12, Mike Christie wrote:
> The atomic use in the main I/O path is causing perf issues when using
> higher performance backend devices and multiple queues (more than
> 10 when using vhost-scsi) like with this fio workload:
> 
> [global]
> bs=4K
> iodepth=128
> direct=1
> ioengine=libaio
> group_reporting
> time_based
> runtime=120
> name=standard-iops
> rw=randread
> numjobs=16
> cpus_allowed=0-15
> 
> To fix this issue, this moves the LUN stats to per CPU.
> 
> Note: I forgot to include this patch with the delayed/ordered per CPU
> tracking and per device/device entry per CPU stats. With this patch you
> get the full 33% improvements when using fast backends, multiple queues
> and multiple IO submiters.
> 
> Signed-off-by: Mike Christie <michael.christie@oracle.com>
> Reviewed-by: Dmitry Bogdanov <d.bogdanov@yadro.com>
> ---
>   drivers/target/target_core_device.c          |  1 +
>   drivers/target/target_core_fabric_configfs.c |  2 +-
>   drivers/target/target_core_internal.h        |  1 +
>   drivers/target/target_core_stat.c            | 67 +++++++-------------
>   drivers/target/target_core_tpg.c             | 23 ++++++-
>   drivers/target/target_core_transport.c       | 22 +++++--
>   include/target/target_core_base.h            |  8 +--
>   7 files changed, 65 insertions(+), 59 deletions(-)
> 
Ho-hum.

That only works if both submission and completion paths do run on the
_same_ cpu. Are we sure that they do?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.com                               +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich

  reply	other threads:[~2025-09-18  6:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 22:12 [PATCH v3 0/3] target: RW/num_cmds stats improvements Mike Christie
2025-09-17 22:12 ` [PATCH v3 1/3] scsi: target: Fix lun/device R/W and total command stats Mike Christie
2025-09-17 22:12 ` [PATCH v3 2/3] scsi: target: Create and use macro helpers for per CPU stats Mike Christie
2025-09-17 22:12 ` [PATCH v3 3/3] scsi: target: Move LUN stats to per CPU Mike Christie
2025-09-18  6:31   ` Hannes Reinecke [this message]
2025-09-18 14:50     ` michael.christie
2025-10-16  6:21       ` Hannes Reinecke
2025-10-16 15:21         ` michael.christie
2025-11-05  4:02 ` [PATCH v3 0/3] target: RW/num_cmds stats improvements Martin K. Petersen

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=03e53a96-d94e-4608-b52e-bbd87b8a90af@suse.com \
    --to=hare@suse.com \
    --cc=bvanassche@acm.org \
    --cc=d.bogdanov@yadro.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michael.christie@oracle.com \
    --cc=mlombard@redhat.com \
    --cc=target-devel@vger.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;
as well as URLs for NNTP newsgroup(s).