From: Daniel Walker <dwalker@fifo99.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>, Douglas Gilbert <dgilbert@interlog.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Hannes Reinecke <hare@suse.de>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Mike Christie <michaelc@cs.wisc.edu>,
Joel Becker <joel.becker@oracle.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Boaz Harrosh <bharrosh@panasas.com>,
Florian Haas <florian.haas@linbit.com>,
Philipp Reisner <philipp.reisner@linbit.com>
Subject: Re: [RFC PATCH 0/19] A kernel-level configfs enabled generic target engine for Linux v2.6.32
Date: Fri, 11 Sep 2009 20:17:48 -0700 [thread overview]
Message-ID: <1252725468.28368.54.camel@desktop> (raw)
In-Reply-To: <1252724884.2067.251.camel@haakon2.linux-iscsi.org>
On Fri, 2009-09-11 at 20:08 -0700, Nicholas A. Bellinger wrote:
>
> Ok, I will have a look at converting the HBA semaphore to a mutex in
> patch 5, and use some single use waitqueues in patch 16. Btw, the ones
> using init_MUTEX_LOCKED() in the latter source file are being used when
> shutting down target_core_mod allocated kernel threads to sychronize
> between the stopping processing threads and configfs process context
> that waitqueues would work better for. Thanks for pointing this out!
You could also use completions in patch 16 if the waitqueues turn out to
be not what your looking for. Completion can sometimes be a find&replace
substitute for the locked semaphores.
> I was thinking about going through the typedefs with a sed chainsaw, but
> I decided against for this TCM patch series because it makes keeping
> backward ports to <= v2.6.31 slightly easier to maintain for me for the
> current users of LIO kernel code.
>
> However, I have been starting to not use typedef for the newest ALUA and
> pieces of PR code, and I would be happy to have another look at typedef
> style comments on this once the other larger interest items are on the
> way to being resolved.
It's up to you, but you should schedule the typedefs for removal at some
point.
Daniel
next prev parent reply other threads:[~2009-09-12 3:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 1:55 [RFC PATCH 0/19] A kernel-level configfs enabled generic target engine for Linux v2.6.32 Nicholas A. Bellinger
2009-09-12 2:37 ` Daniel Walker
2009-09-12 3:08 ` Nicholas A. Bellinger
2009-09-12 3:17 ` Daniel Walker [this message]
2009-09-12 3:24 ` Nicholas A. Bellinger
2009-09-13 10:10 ` Boaz Harrosh
2009-09-14 19:59 ` Nicholas A. Bellinger
2009-09-14 18:50 ` Vladislav Bolkhovitin
2009-09-14 20:49 ` Nicholas A. Bellinger
2009-09-15 18:08 ` Vladislav Bolkhovitin
2009-09-14 20:12 ` Chetan.Loke
2009-09-14 21:06 ` Nicholas A. Bellinger
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=1252725468.28368.54.camel@desktop \
--to=dwalker@fifo99.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=dgilbert@interlog.com \
--cc=florian.haas@linbit.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=greg@kroah.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=joel.becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=philipp.reisner@linbit.com \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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