From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
scsi <linux-scsi@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Schmitz <schmitzmic@gmail.com>
Subject: Re: [PATCH 3/3] scsi/ncr5380: Improve interrupt latency during PIO tranfers
Date: Mon, 29 Aug 2016 14:06:09 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1608291219110.20939@nippy.intranet> (raw)
In-Reply-To: <CAMuHMdUwLAJJUO6L9gKYU4w_RO4s38xzjpRehnNBJPQ7s1+MkA@mail.gmail.com>
On Sun, 28 Aug 2016, Geert Uytterhoeven wrote:
> Hi Finn,
>
> On Sat, Aug 27, 2016 at 4:30 AM, Finn Thain <fthain@telegraphics.com.au>
> wrote:
> > Large PIO transfers are broken up into chunks to try to avoid
> > disabling local IRQs for long periods. But IRQs are still disabled for
> > too long and this causes SCC FIFO overruns during serial port
> > transfers. This patch fixes the problem by halving the PIO chunk size.
> >
> > Testing with mac_scsi shows that the extra NCR5380_main() loop
> > iterations have negligible performance impact on SCSI transfers (about
> > 1% slower). On a faster system (using the dmx3191d module) transfers
> > showed no measurable change.
> >
> > Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
> >
> > ---
> > drivers/scsi/NCR5380.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > Index: linux/drivers/scsi/NCR5380.c
> > ===================================================================
> > --- linux.orig/drivers/scsi/NCR5380.c 2016-08-27 12:29:57.000000000 +1000
> > +++ linux/drivers/scsi/NCR5380.c 2016-08-27 12:29:58.000000000 +1000
> > @@ -1847,11 +1847,11 @@ static void NCR5380_information_transfer
> > /* XXX - need to source or sink data here, as appropriate */
> > }
> > } else {
> > - /* Break up transfer into 3 ms chunks,
> > - * presuming 6 accesses per handshake.
> > + /* Transfer a small chunk so that the
> > + * irq mode lock is not held too long.
> > */
> > transfersize = min((unsigned long)cmd->SCp.this_residual,
> > - hostdata->accesses_per_ms / 2);
> > + hostdata->accesses_per_ms >> 2);
>
> I think it's easier to read if you use "/ 4".
I think the factor, "1/4 byte milliseconds per access" is not very
meaningful. The PIO transfersize can be understood as,
pio_bytes_until_scc_fifo_overflow = accesses_per_ms /
(accesses_per_pio_byte / ms_until_fifo_overflow)
This loop seemed like a good place to avoid a DIV instruction (though I
didn't try to confirm that) and so I used a bit shift to indicate that
intention.
The shift amount was an empirical result that happened to work for the
hardware I tested it on, at the baud rate I was using. Admittedly, if we
want to avoid further tweaks to this then I'll have to do more testing and
find a better approximation.
--
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2016-08-29 4:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 2:29 [PATCH 0/3] Small fixes and cleanup Finn Thain
2016-08-27 2:29 ` [PATCH 1/3] documentation/scsi: Remove nodisconnect parameter Finn Thain
2016-08-28 8:07 ` Geert Uytterhoeven
2016-09-06 12:41 ` Jonathan Corbet
2016-08-27 2:30 ` [PATCH 2/3] scsi/ncr5380: Avoid a compiler warning Finn Thain
2016-08-28 8:08 ` Geert Uytterhoeven
2016-08-27 2:30 ` [PATCH 3/3] scsi/ncr5380: Improve interrupt latency during PIO tranfers Finn Thain
2016-08-28 8:08 ` Geert Uytterhoeven
2016-08-29 4:06 ` Finn Thain [this message]
2016-08-31 4:44 ` [PATCH v2 " Finn Thain
2016-08-31 14:07 ` Laurence Oberman
2016-09-09 11:28 ` Martin K. Petersen
2016-09-09 12:00 ` Geert Uytterhoeven
2016-09-14 18:12 ` Martin K. Petersen
2016-08-31 4:26 ` [PATCH 0/3] Small fixes and cleanup Martin K. Petersen
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=alpine.LNX.2.00.1608291219110.20939@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=schmitzmic@gmail.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
all inboxes | Powered by JetHome®