From: Jens Axboe <axboe@suse.de>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] reworked IDE/general tagged command queueing
Date: Wed, 1 May 2002 20:25:44 +0200 [thread overview]
Message-ID: <20020501182544.GF811@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0205010900050.4589-100000@home.transmeta.com> <3CD0119D.1080905@evision-ventures.com> <3CD02139.3020009@evision-ventures.com>
On Wed, May 01 2002, Martin Dalecki wrote:
> >Well after a short cross over look at it I agree.
> >The generic interface looks sane for me as well. However
> >I will have to look a bit deeper, becouse at the first sight
> >the double pointer to tag_index looks a bit "overelaborate"
> >to me. But I may change my opinnion after looking at the
> >actual usage - so please take this small bit of critique
> >with a good grain of salt...
> >
> >+#define BLK_TAGS_PER_LONG (sizeof(unsigned long) * 8)
> >+#define BLK_TAGS_MASK (BLK_TAGS_PER_LONG - 1)
> >+
> >+struct blk_queue_tag {
> >+ struct request **tag_index; /* map of busy tags */
> >+ unsigned long *tag_map; /* bit map of free/busy tags */
> >+ struct list_head busy_list; /* fifo list of busy tags */
> >+ int busy; /* current depth */
> >+ int max_depth;
> >+};
> >+
>
> Well I revoke my objections. tag_index is fine :-).
It should be, it's just an index of pointer to request, so no double
indirections :)
--
Jens Axboe
next prev parent reply other threads:[~2002-05-01 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 12:37 [PATCH] reworked IDE/general tagged command queueing Jens Axboe
2002-05-01 16:08 ` Linus Torvalds
2002-05-01 16:02 ` Martin Dalecki
2002-05-01 17:09 ` Martin Dalecki
2002-05-01 18:25 ` Jens Axboe [this message]
2002-05-01 18:25 ` Jens Axboe
2002-05-01 16:22 ` Martin Dalecki
2002-05-01 19:08 ` 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=20020501182544.GF811@suse.de \
--to=axboe@suse.de \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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