mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bill Rugolsky Jr." <bill@rugolsky.com>
To: Dan Carpenter <error27.lkml@gmail.com>
Cc: Matt Heler <lkml@lpbproductions.com>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH][INCOMPLETE] sata_nv: merge ADMA support
Date: Fri, 9 Jun 2006 11:32:12 -0400	[thread overview]
Message-ID: <20060609153212.GA28830@ti64.telemetry-investments.com> (raw)
In-Reply-To: <b263e5900606071509o3b06c7a4y84aae7802a5aece2@mail.gmail.com>

On Wed, Jun 07, 2006 at 03:09:31PM -0700, Dan Carpenter wrote:
> Bill Rugolsky Jr. <bill@rugolsky.com> wrote:
> >Here is an incomplete attempt to get the sata_nv ADMA code working.
> >
> >I made another pass through my merge of the sata_nv driver to fix and
> >clean up a few things.  I've only made the minimal changes necessary
> >to get it into a testable state; methinks it could do with a lot of
> >refactoring and cleanup, instead of all the "if (host->...host_type == 
> >ADMA)" tests.
> >
> 
> Did you ever figure this out?
> 
> It looks like you're mixing two completely seperate bugs.  The ata
> timeouts and the lost ticks messages.
> 
> >BIOS Information
> >        Vendor: Phoenix Technologies Ltd.
> >        Version: 2004Q3
> >        Release Date: 10/12/2005
> >
> 
> This is causing the sata failures:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190856
> Downgrade to match your other system (version 1.01).  That will fix
> the ata timeouts at least.

Interesting; I still have one such machine set aside for testing purposes,
so I can give that a try; in my limited testing, ADMA didn't exhibit the
same long latencies.

I'm just rolling up a 2.6.17 kernel patchset, so I'll pull in Jeff's
sata_nv branch and give it a try; the patch queue is long though, so
it will probably be sometime next week.

> I'm still interested in the lost ticks messages though...

My workaround has been to just use John Stultz's new timekeeping
code (actually the variant in Thomas Gleixner's hrtimers rollup --
http://tglx.de/projects/hrtimers/).  Our PostgreSQL servers now maintain
sub-millisecond NTP offsets, whereas previously they would drift 100+ms away,
lose sync, and require an NTP restart every day or so.

John wrote the other day:

   With the current code in -mm I can run a test app that disables
   interrupts for 2 seconds at a time over and over and I'm still keeping
   synched w/ an NTP server within 30 microseconds.

The patches in -mm are set to be merged in 2.6.18-rc1, so I have no qualms
about including them in my internal 2.6.17 patchset.

Kudos to John, Thomas, Ingo, and others who have worked on the new
timekeeping code.  This is yet another area where work on the -rt kernel
benefits everyone in a measurable way.

	-Bill

      reply	other threads:[~2006-06-09 15:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 23:23 Bill Rugolsky Jr.
2006-03-18  0:56 ` Jeff Garzik
2006-03-18  8:06   ` Bill Rugolsky Jr.
2006-03-18  8:56     ` Jeff Garzik
2006-03-19 23:23       ` Bill Rugolsky Jr.
2006-03-21  1:28         ` Jeff Garzik
2006-03-21 12:48           ` Bill Rugolsky Jr.
2006-03-27  1:14           ` Matt Heler
2006-03-27 16:08             ` Bill Rugolsky Jr.
2006-03-27 21:46               ` Matt Heler
2006-03-27 22:00                 ` Matt Heler
2006-03-30  1:23                   ` Alexander Samad
2006-06-07 22:09               ` Dan Carpenter
2006-06-09 15:32                 ` Bill Rugolsky Jr. [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=20060609153212.GA28830@ti64.telemetry-investments.com \
    --to=bill@rugolsky.com \
    --cc=error27.lkml@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@lpbproductions.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®