From: Johannes Thumshirn <jthumshirn-l3A5Bk7waGM@public.gmane.org>
To: Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Mike Christie <michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>,
"Nicholas A. Bellinger"
<nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>,
Lee Duncan <lduncan-IBi9RG/b67k@public.gmane.org>,
Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>,
Jayamohan Kallickal
<jayamohan.kallickal-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org>
Cc: linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: iSCSI and scsi-mq
Date: Wed, 25 Nov 2015 11:04:25 +0100 [thread overview]
Message-ID: <1448445865.2877.71.camel@suse.de> (raw)
Hi iSCSI experts,
I've been starting to research possible implementations of a scsi-mq capable
iSCSI. With my research I found the following thread https://groups.google.com/
forum/#!msg/open-iscsi/qLaXJh2Gqt4/A2NIDZ0fT9oJ and wondered what happened to
the efforts layed out there (and what have been the results of the discussion
at LSF/MM).
The one TCP connection per CPU or HW queue approach sounds particularly
interesting to me when taking a SW iSCSI initiator. A problem Hannes pointed
out here could be network topology changes which result in a different route on
a different NIC with a different number of HW queues, so it might not be the
ultimate solution.
With the offload cards we might need to do something else.
Is there anyone else working on a scsi-mq for iSCSI at the moment and is
willing to join efforts here?
Byte,
Johannes
--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
reply other threads:[~2015-11-25 10:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1448445865.2877.71.camel@suse.de \
--to=jthumshirn-l3a5bk7wagm@public.gmane.org \
--cc=hare-l3A5Bk7waGM@public.gmane.org \
--cc=jayamohan.kallickal-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org \
--cc=lduncan-IBi9RG/b67k@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org \
--cc=nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org \
--cc=open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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 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.