From: Vasily Averin <vvs@sw.ru>
To: adam radford <aradford@gmail.com>
Cc: Adam Radford <aradford@amcc.com>, linuxraid <linuxraid@amcc.com>,
James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org, devel@openvz.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [SCSI] 3w-9xxx: kmap_atomic in twa_scsiop_execute_scsi
Date: Tue, 06 Jun 2006 23:28:27 +0400 [thread overview]
Message-ID: <4485D75B.7070902@sw.ru> (raw)
In-Reply-To: <b1bc6a000606061146p7a26aca9o62f9a8c22ffb0c63@mail.gmail.com>
Adam,
adam radford wrote:
> Vasily,
>
> On 6/5/06, Vasily Averin <vvs@sw.ru> wrote:
>
>> I'm agree that queuecommand() executed with disabled interrupts. However
>> twa_scsiop_execute_scsi() can be called not only from queuecommand.
>> For example,
>>
>> twa_interrupts (note: with _enabled_ interrupts)
>> twa_aen_read_queue
>> twa_scsiop_execute_scsi
>>
>
> twa_scsiop_execute_scsi() will not perform the
> kmap_atomic()/kunmap_atomic()
> calls here because it is being used for an internal AEN drain (cdb
> post), i.e. "sglistarg" is non NULL. See below:
>
> if (!sglistarg) {
>
> ....
> kmap_atomc()
> kunmap_atomic()
>
> } else {
> /* Internal cdb post */
>
> }
Ok, I'm agree.
Thank you for your explanation,
Vasily Averin
SWsoft Virtuozzo/OpenVZ Linux kernel team
next prev parent reply other threads:[~2006-06-06 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DB599F406D04E34389140B7D99C71B1B0203D625@SDCEXCHANGE01.ad.amcc.com>
2006-06-06 5:49 ` [SCSI] 3w-9xxx: kmap_atomic in twa_scsiop_execute_scsi Vasily Averin
2006-06-06 18:46 ` adam radford
2006-06-06 19:28 ` Vasily Averin [this message]
2006-06-04 8:49 Vasily Averin
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=4485D75B.7070902@sw.ru \
--to=vvs@sw.ru \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=aradford@amcc.com \
--cc=aradford@gmail.com \
--cc=devel@openvz.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxraid@amcc.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).