All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>,
	James Bottomley <JBottomley@Parallels.com>,
	Jun Itou <itou_jun@infoseek.jp>,
	Markus Rathgeb <maggu2810@gmail.com>, Matt <vickm78@hotmail.com>,
	SCSI development list <linux-scsi@vger.kernel.org>,
	USB Storage list <usb-storage@lists.one-eyed-alien.net>,
	USB list <linux-usb@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] USB: storage: add "no SYNCHRONIZE CACHE" quirk
Date: Fri, 26 Jun 2015 13:05:05 +0200	[thread overview]
Message-ID: <20150626130505.3918c5a9@kant> (raw)
In-Reply-To: <1435313657.2211.70.camel@HansenPartnership.com>

On Jun 26 James Bottomley wrote:
> On Fri, 2015-06-26 at 11:43 +0200, Stefan Richter wrote:
> > On Jun 22 James Bottomley wrote:
[...]
> > > Perhaps it might be wise to do this to every USB device ... for external
> > > devices, the small performance gain doesn't really make up for the
> > > potential data loss.
> > 
> > Just a small note on the assumption of externally (and in extension,
> > temporarily) attached devices:  Not all USB-attached devices are external,
> > and not all external devices are used as removable devices.
> 
> The problems don't depend on the connection type: internal devices which
> have a writeback cache and don't accept flush commands have data
> integrity problems too.  I can't really think of many situations where
> you'd be willing to sacrifice data integrity for performance.

Sure; writeback caches are prone to more issues besides sudden connection
loss.  (E.g. sudden power loss is but one of several more potential issues
of course.)

I merely wanted to remind that the bus type of a device (USB or whatever)
does not say much about the risk of sudden connection loss to that device,
since such devices may have physical protection against sudden connection
loss too.  I was not particularly commenting on the topic at hand, i.e.
on presence of writeback cache without working flush command.
-- 
Stefan Richter
-=====-===== -==- ==-=-
http://arcgraph.de/sr/

      reply	other threads:[~2015-06-26 11:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 14:55 [PATCH] USB: storage: add "no SYNCHRONIZE CACHE" quirk Alan Stern
2015-06-22 15:43 ` James Bottomley
2015-06-22 17:30   ` Alan Stern
2015-06-22 17:36     ` James Bottomley
     [not found]       ` <1434994588.2237.90.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2015-06-22 17:48         ` Alan Stern
2015-06-22 18:44           ` Markus Rathgeb
     [not found]             ` <CAOcK=COj7=akJUhsg2Pfr5aeh_tC9dEL3rZK1yKuvTN0KyJB1A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-22 20:16               ` Alan Stern
2015-06-22 21:32                 ` Markus Rathgeb
     [not found]           ` <Pine.LNX.4.44L0.1506221340180.1799-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2015-06-22 21:22             ` James Bottomley
     [not found]               ` <1435008177.2237.137.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2015-07-24 15:19                 ` Alan Stern
2015-12-03 18:36               ` Alan Stern
2015-12-15 11:34                 ` Oliver Neukum
     [not found]                   ` <1450179271.17387.19.camel-IBi9RG/b67k@public.gmane.org>
2015-12-15 15:16                     ` Alan Stern
2015-06-23 14:15         ` David Laight
2015-06-26  9:43         ` Stefan Richter
2015-06-26 10:14           ` James Bottomley
2015-06-26 11:05             ` Stefan Richter [this message]

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=20150626130505.3918c5a9@kant \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=JBottomley@Parallels.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=axboe@kernel.dk \
    --cc=greg@kroah.com \
    --cc=itou_jun@infoseek.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=maggu2810@gmail.com \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    --cc=vickm78@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.