From: Mike Christie <michaelc@cs.wisc.edu>
To: Doug Maxey <dwm@bebe.enoyolf.org>
Cc: Ravi Anand <ravi.anand@qlogic.com>,
David Somayajulu <davidcs2005@gmail.com>,
Duane Grigsby <duane.grigsby@qlogic.com>,
linux-scsi@vger.kernel.org, dwm@austin.ibm.com
Subject: Re: [RFC] qla4xxx: TODO for re-submission
Date: Mon, 12 Jun 2006 13:05:09 -0500 [thread overview]
Message-ID: <448DACD5.6090205@cs.wisc.edu> (raw)
In-Reply-To: <8889.1149988615@bebe.enoyolf.org>
Doug Maxey wrote:
> 5) add the block layer code.
Some related issues that we have discussed offlist about this and should
probably be discussed here are:
- Are we supposed to follow FC's lead and remove the devices (rport,
session, target, scsi_device, etc) if the dev_loss_tmo fires. Currently
for software iscsi, we leave the devices/session. This was to reduce
memory allocations and because software iscsi has to basically poll the
connection during connect as part of the relogin process. So unlike FC
or hw iscsi, if we remove the devices/structs we have to end up
rebuilding some of them right away anyways.
Removing the devices has the benefit of simplifying the scsi/iscsi code.
- Scanning. We currently do scanning for open-iscsi in userspace. For
iscsi root this requires distro support. SUSE has it. Fedora is working
on it. There is also Debian and Gentoo users or maintainers posting
about working on it. For qla4xxx, we could stick the scanning in the
kernel like FC and distros would not have to worry about it, but since
they have to get this working for software iscsi do we just keep the
scanning in userspace?
next prev parent reply other threads:[~2006-06-12 18:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 1:16 [RFC] qla4xxx: TODO for re-submission Doug Maxey
2006-06-12 16:49 ` Ravi Anand
2006-06-12 16:52 ` Mike Christie
2006-06-12 16:57 ` Ravi Anand
2006-06-12 19:08 ` Doug Maxey
2006-06-12 19:01 ` Doug Maxey
2006-06-12 17:43 ` Mike Christie
2006-06-12 17:44 ` Mike Christie
2006-06-12 19:04 ` Doug Maxey
2006-06-12 20:05 ` Mike Christie
2006-06-12 18:05 ` Mike Christie [this message]
2006-06-12 21:10 ` Ravi Anand
2006-06-12 21:35 ` Mike Christie
2006-06-12 22:35 ` Mike Christie
2006-06-12 22:50 ` Ravi Anand
2006-06-12 22:43 ` Ravi Anand
2006-06-13 3:30 ` Mike Christie
2006-06-13 3:48 ` Doug Maxey
2006-06-13 4:31 ` Jeff Garzik
2006-06-13 5:00 ` Doug Maxey
2006-06-13 12:16 ` berthiaume_wayne
2006-06-15 0:35 ` Ravi Anand
2006-06-15 0:43 ` Ravi Anand
2006-06-15 17:31 ` Mike Christie
-- strict thread matches above, loose matches on Subject: below --
2006-06-16 22:32 David Somayajulu
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=448DACD5.6090205@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=davidcs2005@gmail.com \
--cc=duane.grigsby@qlogic.com \
--cc=dwm@austin.ibm.com \
--cc=dwm@bebe.enoyolf.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ravi.anand@qlogic.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 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).