From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/4] sd: fix cache flushing message
Date: Wed, 29 Apr 2009 22:53:07 +0200 [thread overview]
Message-ID: <200904292253.07817.bzolnier@gmail.com> (raw)
In-Reply-To: <49F8B71B.90707@garzik.org>
On Wednesday 29 April 2009 22:22:51 Jeff Garzik wrote:
> James Bottomley wrote:
> > On Wed, 2009-04-29 at 22:06 +0200, Bartlomiej Zolnierkiewicz wrote:
> >> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> >> ---
> >> some minor sd.c fixups against linux-next
> >>
> >> drivers/scsi/sd.c | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> Index: b/drivers/scsi/sd.c
> >> ===================================================================
> >> --- a/drivers/scsi/sd.c
> >> +++ b/drivers/scsi/sd.c
> >> @@ -2140,7 +2140,7 @@ static void sd_shutdown(struct device *d
> >> return; /* this can happen */
> >>
> >> if (sdkp->WCE) {
> >> - sd_printk(KERN_NOTICE, sdkp, "Synchronizing SCSI cache\n");
> >> + sd_printk(KERN_NOTICE, sdkp, "Synchronizing disk cache\n");
> >> sd_sync_cache(sdkp);
> >> }
> >>
> >> @@ -2161,7 +2161,7 @@ static int sd_suspend(struct device *dev
> >> return 0; /* this can happen */
> >>
> >> if (sdkp->WCE) {
> >> - sd_printk(KERN_NOTICE, sdkp, "Synchronizing SCSI cache\n");
> >> + sd_printk(KERN_NOTICE, sdkp, "Synchronizing disk cache\n");
> >> ret = sd_sync_cache(sdkp);
> >> if (ret)
> >> goto done;
> >
> > So you want it to say
> >
> > sda: synchronizing disk cache
> >
> > instead of
> >
> > sda: synchronizing SCSI cache
> >
> > I don't really see that buying us anything in terms of clarity. What's
> > the actual problem it solves?
Inconsistent kernel messages:
if (sdkp->WCE) {
sd_printk(KERN_NOTICE, sdkp, "Synchronizing SCSI cache\n");
sd_sync_cache(sdkp);
}
if (system_state != SYSTEM_RESTART && sdkp->device->manage_start_stop) {
sd_printk(KERN_NOTICE, sdkp, "Stopping disk\n");
sd_start_stop_device(sdkp, 0);
}
> Indeed.
>
> And we can argue for weeks about English text, too. Non-disk devices
Or we can just apply the patch and go back with the program.
> like SSDs have caches too, so I'd say "SCSI cache" is more accurate than
> "disk cache". But maybe "SCSI writeback cache" would be even better.
Could you please explain me what *SCSI* cache is?
Does ATA disks have *SCSI* cache (whatever it is)?
Please also note that sd.c uses "disk" all over the place.
Thanks,
Bart
next prev parent reply other threads:[~2009-04-29 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 20:06 [PATCH 1/4] sd: fix cache flushing message Bartlomiej Zolnierkiewicz
2009-04-29 20:20 ` James Bottomley
2009-04-29 20:22 ` Jeff Garzik
2009-04-29 20:36 ` Matthew Wilcox
2009-04-29 20:41 ` Martin K. Petersen
2009-04-29 20:53 ` Bartlomiej Zolnierkiewicz [this message]
2009-04-29 21:14 ` James Bottomley
2009-04-29 21:54 ` Bartlomiej Zolnierkiewicz
2009-04-30 11:35 ` Douglas Gilbert
2009-04-30 12:32 ` Bartlomiej Zolnierkiewicz
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=200904292253.07817.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jeff@garzik.org \
--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;
as well as URLs for NNTP newsgroup(s).