All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François romieu" <romieu@zoreil.com>
To: "Robert J.Dunlop" <rjd@xyzzy.clara.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FarSync T-Series tweak and question
Date: Fri, 27 Jul 2001 18:11:27 +0200	[thread overview]
Message-ID: <20010727181127.A5157@zoreil.com> (raw)
In-Reply-To: <20010703182803.A13853@xyzzy.clara.co.uk> <20010704161845.A27070@zoreil.com> <20010709161947.B15379@xyzzy.clara.co.uk> <20010726155123.A5815@xyzzy.clara.co.uk>
In-Reply-To: <20010726155123.A5815@xyzzy.clara.co.uk>; from rjd@xyzzy.clara.co.uk on Thu, Jul 26, 2001 at 03:51:23PM +0100

The Thu, Jul 26, 2001 at 03:51:23PM +0100, Robert J.Dunlop wrote :
[...]
> > > +        if ( ++port->txpos >= NUM_TX_BUFFER )
> > > +                port->txpos = 0;
[...]
> > I think mine is clearer but then I've always bumped and wrapped pointers and
> > indexs that way. Another alternative would be:
> >     port->txpos = ( port->txpos + 1 ) % NUM_TX_BUFFER;
> 
> Having taken the time that the % operation wouldn't be detrimental on other
> processor architectures and having checked with a small test that the
> alternate form produced tighter code on Intel I applied the change to my 
> driver.  The code that had shrunk in a small test got bigger (and slower?) 
> in the driver :-(

Have you the .o at hand ? I'd be curious to objdump them.
Btw, I don't believe either expression impacts the perfs. During init,
it's not time critical and while processing data, it looks like the driver 
does himself the dma with the adapter.

--
Ueimor

      reply	other threads:[~2001-07-27 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 17:28 New FarSync T-Series driver Robert J.Dunlop
2001-07-04 14:18 ` François romieu
2001-07-09 15:19   ` Robert J.Dunlop
2001-07-26 14:51     ` FarSync T-Series tweak and question Robert J.Dunlop
2001-07-27 16:11       ` François romieu [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=20010727181127.A5157@zoreil.com \
    --to=romieu@zoreil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjd@xyzzy.clara.co.uk \
    /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.