All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michael.christie@oracle.com>
To: lduncan@suse.com, cleech@redhat.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, jejb@linux.ibm.com
Subject: [PATCH 0/9] iscsi features for 5.20
Date: Thu, 16 Jun 2022 17:45:48 -0500	[thread overview]
Message-ID: <20220616224557.115234-1-michael.christie@oracle.com> (raw)

The following patches are for 5.20. They were built against Linus's tree
but they have no conflicts with the existing patches on the list and
can be applied before or after those patches. The patches also apply over
Martin's staging and queueing branches.

The bulk of the patches allow us to run from a workqueue instead of always
running from the net softirq. When using lots of sessions we see a nice
perf bump when doing throughput and IOPs tests. There's then some cleanups
and locking improvements.



             reply	other threads:[~2022-06-16 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 22:45 Mike Christie [this message]
2022-06-16 22:45 ` [PATCH 1/9] scsi: iscsi: Rename iscsi_conn_queue_work() Mike Christie
2022-06-16 22:45 ` [PATCH 2/9] scsi: iscsi: Add recv workqueue helpers Mike Christie
2022-06-16 22:45 ` [PATCH 3/9] scsi: iscsi: Run recv path from workqueue Mike Christie
2022-06-16 22:45 ` [PATCH 4/9] scsi: iscsi_tcp: Tell net when there's more data Mike Christie
2022-06-16 22:45 ` [PATCH 5/9] scsi: iscsi_tcp: Drop target_alloc use Mike Christie
2022-06-16 22:45 ` [PATCH 6/9] scsi: iscsi: Remove unneeded task state check Mike Christie
2022-06-16 22:45 ` [PATCH 7/9] scsi: iscsi: Remove iscsi_get_task back_lock requirement Mike Christie
2022-06-16 22:45 ` [PATCH 8/9] scsi: iscsi: Try to avoid taking back_lock in xmit path Mike Christie
2022-06-16 22:45 ` [PATCH 9/9] scsi: libiscsi: Improve conn_send_pdu API Mike Christie
2022-06-22  1:20 ` [PATCH 0/9] iscsi features for 5.20 Martin K. Petersen
2022-06-28  3:24 ` 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=20220616224557.115234-1-michael.christie@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=cleech@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=lduncan@suse.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.