From: Daniel Walker <danielwa@cisco.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jens Axboe <axboe@kernel.dk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, stable@vger.kernel.org,
xe-linux-external@cisco.com
Subject: Re: usb-storage: Set virt_boundary_mask to avoid SG overflows
Date: Mon, 4 Nov 2019 11:01:23 -0800 [thread overview]
Message-ID: <20191104190123.GG18744@zorba> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1911041344050.1689-100000@iolanthe.rowland.org>
On Mon, Nov 04, 2019 at 01:45:11PM -0500, Alan Stern wrote:
> On Mon, 4 Nov 2019, Daniel Walker wrote:
>
> > Hi,
> >
> > This is a stable defect report.
> >
> > We're tracking v4.9 stable for some of our products (i.e. Cisco Systems, Inc.)
> > We noticed a speed degradation of roughly %30 on writes to a /dev/sdaX device
> > over USB (no file system). We bisected the issue to this commit from Alan Stern.
> > We also found a prior report of speed degradation on NTFS,
> >
> > https://lore.kernel.org/linux-usb/Pine.LNX.4.44L0.1908291030400.1306-100000@iolanthe.rowland.org/T/
> >
> > We have the patch reverted in our v4.9 tree on top of stable. It seems Alan was
> > planning to remove these lines. If the lines are planned to be removed is there
> > an reason why they haven't been ?
>
> See https://marc.info/?l=linux-usb&m=157167288816325&w=2
>
Ok .. Thanks.
Daniel
next prev parent reply other threads:[~2019-11-04 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 18:20 usb-storage: Set virt_boundary_mask to avoid SG overflows Daniel Walker
2019-11-04 18:45 ` Alan Stern
2019-11-04 19:01 ` Daniel Walker [this message]
[not found] <CAHS7XqPfo7kevyCWyAdf+3yg88z-+YWMhHQAPmkbLEaXg7W_PQ@mail.gmail.com>
2019-08-29 14:37 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2019-04-15 17:19 Alan Stern
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=20191104190123.GG18744@zorba \
--to=danielwa@cisco.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=xe-linux-external@cisco.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