linux-kernel - Re: [PATCH 4/6] mpt2sas: store scsi io tracker data in the scsi request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Apr 2015 11:49:44 +0200
From:	Christoph Hellwig <hch@....de>
To:	Jens Axboe <axboe@...com>
Cc:	axboe@...nel.dk, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, hch@....de
Subject: Re: [PATCH 4/6] mpt2sas: store scsi io tracker data in the scsi
	request

On Tue, Apr 07, 2015 at 11:18:38AM -0600, Jens Axboe wrote:
> Instead of storing the IO tracker structure in a separate list
> that we need to pop/push to on every submit and complete (and
> lock), store it in the pdu associated with a request. This is
> possible on scsi-mq only, and further cuts the spinlock associated
> time for higher IOPS IO workloads. At 100K IOPS, this effectively
> cuts the locking time in half.

As mentioned before please call scsi_init_shared_tag_map and use your
new code path for the !mq case as well.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/