From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org
Subject: [PATCH] switch command completion queue to per-cpu data
Date: Mon, 22 Sep 2003 22:39:31 +0200 [thread overview]
Message-ID: <20030922203931.GA30386@lst.de> (raw)
- DEFINE_PER_CPU works in modules now, use it
- rename done_q to scsi_done_q - in the kernel we prefer descriptive
prefixes even for statics..
diff -Nru a/drivers/scsi/scsi.c b/drivers/scsi/scsi.c
--- a/drivers/scsi/scsi.c Sat Sep 20 09:35:19 2003
+++ b/drivers/scsi/scsi.c Sat Sep 20 09:35:19 2003
@@ -535,7 +535,7 @@
/*
* Per-CPU I/O completion queue.
*/
-static struct list_head done_q[NR_CPUS] __cacheline_aligned;
+static DEFINE_PER_CPU(struct list_head, scsi_done_q);
/**
* scsi_done - Enqueue the finished SCSI command into the done queue.
@@ -553,7 +553,6 @@
void scsi_done(struct scsi_cmnd *cmd)
{
unsigned long flags;
- int cpu;
/*
* We don't have to worry about this one timing out any more.
@@ -580,8 +579,7 @@
* and need no spinlock.
*/
local_irq_save(flags);
- cpu = smp_processor_id();
- list_add_tail(&cmd->eh_entry, &done_q[cpu]);
+ list_add_tail(&cmd->eh_entry, &__get_cpu_var(scsi_done_q));
raise_softirq_irqoff(SCSI_SOFTIRQ);
local_irq_restore(flags);
}
@@ -600,7 +598,7 @@
LIST_HEAD(local_q);
local_irq_disable();
- list_splice_init(&done_q[smp_processor_id()], &local_q);
+ list_splice_init(&__get_cpu_var(scsi_done_q), &local_q);
local_irq_enable();
while (!list_empty(&local_q)) {
@@ -1008,7 +1006,7 @@
goto cleanup_sysctl;
for (i = 0; i < NR_CPUS; i++)
- INIT_LIST_HEAD(&done_q[i]);
+ INIT_LIST_HEAD(&per_cpu(scsi_done_q, i));
devfs_mk_dir("scsi");
open_softirq(SCSI_SOFTIRQ, scsi_softirq, NULL);
reply other threads:[~2003-09-22 20:39 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=20030922203931.GA30386@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.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