From: Jens Axboe <axboe@suse.de>
To: "Manfred.Scherer.Mhm@t-online.de" <Manfred.Scherer.Mhm@t-online.de>
Cc: paul@paulbristow.net, linux-kernel@vger.kernel.org,
manfred.scherer@siemens.com
Subject: Re: PATCH for ide_floppy
Date: Fri, 1 Jul 2005 18:15:34 +0200 [thread overview]
Message-ID: <20050701161534.GJ2243@suse.de> (raw)
In-Reply-To: <1DoNSU-0kLq880@fwd18.aul.t-online.de>
On Fri, Jul 01 2005, Manfred.Scherer.Mhm@t-online.de wrote:
> --- linux-2.6.12/drivers/ide/ide-floppy.c.ORIG 2005-06-17
> 21:48:29.000000000 +0200
> +++ linux-2.6.12/drivers/ide/ide-floppy.c 2005-06-25
> 03:29:45.000000000 +0200
> @@ -125,7 +125,14 @@
> /*
> * Some drives require a longer irq timeout.
> */
> +#if 0
> #define IDEFLOPPY_WAIT_CMD (5 * WAIT_CMD)
> +#endif
> +#if 0
> +#define IDEFLOPPY_WAIT_CMD 200 /* --ms */
> +#endif
> +#define IDEFLOPPY_WAIT_CMD WAIT_CMD /* 2004/12/31
> --ms */
> +
>
> /*
> * After each failed packet command we issue a request sense
> command
> @@ -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 */
> +
This seems to be basically what your patch changes, along with the
expiry addition. Neither of which should make any change in performance,
since you should normally not time commands out. Do you normally get
lots of errors or timeouts running that workload?
I don't see how your patch changes anything for a normally running
ide-floppy.
--
Jens Axboe
next prev parent reply other threads:[~2005-07-01 16:14 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 [this message]
2005-07-01 16:58 ` Manfred.Scherer.Mhm
2005-07-01 17:08 ` Bartlomiej Zolnierkiewicz
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=20050701161534.GJ2243@suse.de \
--to=axboe@suse.de \
--cc=Manfred.Scherer.Mhm@t-online.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