From: Ravi Anand <ravi.anand@qlogic.com>
To: Doug Maxey <dwm@enoyolf.org>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
David Somayajulu <david.somayajulu@qlogic.com>,
open-iscsi@googlegroups.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH ver3 3/4] qla4xxx: use dev_xxx on some pci/dma resource alloc warning and error printks
Date: Wed, 9 Aug 2006 16:36:01 -0700 [thread overview]
Message-ID: <20060809233601.GG9156@ranandlinuxbox.qlogic.org> (raw)
In-Reply-To: <20060809230550.480743@bebe.enoyolf.org>
>On Wed, 09 Aug 2006, Doug Maxey wrote:
> On Wed, 09 Aug 2006 13:52:07 EDT, Mike Christie wrote:
> ...
> > > @@ -836,9 +825,8 @@ static int qla4xxx_mem_alloc(struct scsi
> > > ha->srb_mempool = mempool_create(SRB_MIN_REQ, mempool_alloc_slab,
> > > mempool_free_slab, srb_cachep);
> > > if (ha->srb_mempool == NULL) {
> > > - ql4_printk(KERN_WARNING, ha,
> > > - "Memory Allocation failed - SRB Pool.\n");
> > > -
> > > + dev_warn(&ha->pdev->dev,
> > > + "Memory Allocation failed - SRB Pool.\n");
> > > goto mem_alloc_error_exit;
> >
> > Sorry for the late response on this one. As you know I was out for a
> > while and I was waiting to get internet access yesterday.
> >
> > For these host messages, do we want something like the sdev_printk and
> > starget_printk or does it really make more sense to use the pci bus id
> > for the message prefix? What about other scsi host messages, will they
> > always go with the pci bus id or some scsi-ml id? And even if we want to
> > print out the pci bus id as the prefix instead of some scsi info, should
> > we still have some scsi wrapper?
> >
>
> I do agree that iscsi_transport sessions could use a new macro.
>
> My intention in this instance was to go with the widely used idiom, and
> to not have a driver specific one. Was trying to replace
> #define ql4_printk(level, ha, format, arg...) \
> dev_printk(level, &((ha)->pdev->dev), format, ## arg)
>
> But to follow on from irc, one more pass at this to help me clarify and
> understand what is need here.
>
> dev_xxx is a wrapper around dev_print(xxx ...).
>
> In the specific instance above, this should print
> scsiN arg...
>
> Since qla4xxx_mem_alloc() is for the host, would an sdev_printk be
> the right thing? I don't believe we have any context of a target.
> Of course that may be a misunderstanding on my part.
>
> For this driver, I don't see any instances of a scsi_target.
You are correct. Its during init time. So you dont have any instance of scsi_target.
Ravi
next prev parent reply other threads:[~2006-08-09 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060805225156.9557.99072.stgit@bebe.enoyolf.org>
2006-08-05 22:52 ` [PATCH ver3 1/4] qla4xxx: Remove funcs with no callers in ql4_init.c Doug Maxey
2006-08-05 22:52 ` [PATCH ver3 2/4] qla4xxx: Add a timeout period and return status from ql4xxx_lock_drvr_wait() Doug Maxey
2006-08-05 22:52 ` [PATCH ver3 3/4] qla4xxx: use dev_xxx on some pci/dma resource alloc warning and error printks Doug Maxey
2006-08-09 17:52 ` Mike Christie
2006-08-09 19:03 ` Doug Maxey
2006-08-09 23:05 ` Doug Maxey
2006-08-09 23:36 ` Ravi Anand [this message]
2006-08-10 9:52 ` Mike Christie
2006-08-10 10:18 ` Mike Christie
2006-08-10 13:59 ` James Bottomley
2006-08-05 22:52 ` [PATCH ver3 4/4] qla4xxx: improve symmetry in buffer codepaths Doug Maxey
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=20060809233601.GG9156@ranandlinuxbox.qlogic.org \
--to=ravi.anand@qlogic.com \
--cc=david.somayajulu@qlogic.com \
--cc=dwm@enoyolf.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=open-iscsi@googlegroups.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