From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Manfred.Scherer.Mhm@t-online.de" <Manfred.Scherer.Mhm@t-online.de>
Cc: Jens Axboe <axboe@suse.de>,
paul@paulbristow.net, linux-kernel@vger.kernel.org,
manfred.scherer@siemens.com
Subject: Re: Re: PATCH for ide_floppy
Date: Fri, 1 Jul 2005 19:08:58 +0200 [thread overview]
Message-ID: <58cb370e050701100839b01186@mail.gmail.com> (raw)
In-Reply-To: <1DoOqm-0TquC80@fwd16.aul.t-online.de>
On 7/1/05, Manfred.Scherer.Mhm@t-online.de
<Manfred.Scherer.Mhm@t-online.de> wrote:
> it's not really a performance issue but more a timeout issue.
> 'IDEFLOPPY_TICKS_DELAY 60' avoids error messages in /var/log/messages
> like 'reset ide ...'.
> Without the idefloppy_timer_expiry the data transfer to the ide-floppy
> is pending a long time between some transfer of data. The floppy LED
> indicated this too.
> With kernel 2.4.x I've never had this problem.
This seems related to 2.4 -> 2.6 HZ change.
> > @@ -317,7 +324,13 @@
> > unsigned long flags;
> > } idefloppy_floppy_t;
> >
> > +#if 0
> > #define IDEFLOPPY_TICKS_DELAY 3 /* default delay for ZIP 100
> */
> > +#define IDEFLOPPY_TICKS_DELAY 6 /* default delay for ZIP 100
> > --ms 2005/01/01 */
> > +#define IDEFLOPPY_TICKS_DELAY 12 /* default delay for ZIP 100
> > --ms 2005/01/01 */
> > +#endif
> > +#define IDEFLOPPY_TICKS_DELAY 60 /* default delay for ZIP 100
> > --ms 2005/01/07 */
> > +
"ticks" delay should be expressed using HZ
#define IDEFLOPPY_TICKS_DELAY HZ/20
for 50msec delay (N.B. the comment in the code about default delay
being 50msec also seems wrong - it was more like ~33msec in 2.4)
Could you please test if this fixes your problems?
Bartlomiej
next prev parent reply other threads:[~2005-07-01 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 15:29 PATCH for ide_floppy Manfred.Scherer.Mhm
2005-07-01 16:15 ` Jens Axboe
2005-07-01 16:58 ` Manfred.Scherer.Mhm
2005-07-01 17:08 ` Bartlomiej Zolnierkiewicz [this message]
2005-07-04 9:41 ` Manfred.Scherer.Mhm
2005-07-01 17:41 ` Jens Axboe
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=58cb370e050701100839b01186@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=Manfred.Scherer.Mhm@t-online.de \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred.scherer@siemens.com \
--cc=paul@paulbristow.net \
/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