From: Jens Axboe <axboe@suse.de>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.1-rc2 ide barrier support
Date: Thu, 8 Jan 2004 09:31:12 +0100 [thread overview]
Message-ID: <20040108083112.GN16720@suse.de> (raw)
In-Reply-To: <200401071945.04649.bzolnier@elka.pw.edu.pl>
On Wed, Jan 07 2004, Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 07 of January 2004 14:43, Jens Axboe wrote:
> > Bart, would you care to review the ide bits for sanity?
>
> Yep, here is just a first sight...
>
> > + struct request *flush_rq = &HWGROUP(drive)->wrq;
>
> I want to remove drive->wrq in the future.
Yes I've wanted that, too, but only because of the ugly (and often racy)
multimode crap. I'm just considering wrq a 'reserve rq' to be used where
you cannot reliably get a new request atomically.
I'm open to any better ideas you have for this...
> > + memset(drive->special_buf, 0, sizeof(drive->special_buf));
> > +
> > + ide_init_drive_cmd(flush_rq);
> > +
> > + flush_rq->flags = REQ_DRIVE_TASK;
> > + flush_rq->buffer = drive->special_buf;
> > + flush_rq->special = rq;
> > + flush_rq->buffer[0] = WIN_FLUSH_CACHE;
> > + flush_rq->nr_sectors = rq->nr_sectors;
>
> I think you should try use REQ_DRIVE_TASKFILE,
> instead of adding drive->special_buf.
How does that change anything? I still need a command buffer, if I use
REQ_DRIVE_TASKFILE I need an even bigger one.
> > +/*
> > + * FIXME: probably move this somewhere else, name is bad too :)
> > + */
> > +static sector_t ide_get_error_location(ide_drive_t *drive, char *args)
>
> This is probably useful in few other places.
Yeah, as the comment states I know it's not really in the right place.
Where do you want it? And any suggestions for a better name? :)
--
Jens Axboe
next prev parent reply other threads:[~2004-01-08 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 13:43 [PATCH] 2.6.1-rc2 ide barrier support Jens Axboe
2004-01-07 18:45 ` Bartlomiej Zolnierkiewicz
2004-01-08 8:31 ` Jens Axboe [this message]
2004-01-09 2:34 ` Benjamin Herrenschmidt
2004-01-09 7:26 ` Jens Axboe
2004-01-09 13:45 ` Benjamin Herrenschmidt
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=20040108083112.GN16720@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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