From: Martin Dalecki <dalecki@evision-ventures.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alexander Viro <viro@math.psu.edu>, Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] change of ->bd_op->open() semantics
Date: Fri, 24 May 2002 23:15:56 +0200 [thread overview]
Message-ID: <3CEEAD8C.1060202@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205241323240.11918-100000@home.transmeta.com>
Uz.ytkownik Linus Torvalds napisa?:
>
> On Fri, 24 May 2002, Alexander Viro wrote:
>
>> It has an additional benefit of killing the array of default
>>queues on the same pass - a thing we will need to do sooner or later
>>anyway.
>
>
> I'd like to see this, because we want to make the "find the right queue" a
> much more expensive operation (no longer some fairly simple mapping from
> major number - a more dynamic and general "register this queue for minors
> xxxx-yyyy of major zzz").
>
> Doing it just once at open() time allows for that to happen without any
> performance downside.
>
> Linus
Current ATA code says about this:
/*
* Returns the queue which corresponds to a given device.
*
* FIXME: this should take struct block_device * as argument in future.
*/
static request_queue_t *ata_get_queue(kdev_t dev)
{
struct ata_channel *ch = (struct ata_channel *)blk_dev[major(dev)].data;
/* FIXME: ALLERT: This discriminates between master and slave! */
return &ch->drives[DEVICE_NR(dev) & 1].queue;
}
Guess who did spill the FIXME: entiers there?
So of course plese plese go ahead as soon as possible!.
I would love to don't have to look at the above any longer.
next prev parent reply other threads:[~2002-05-24 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 20:12 [RFC] change of ->bd_op->open() semantics Alexander Viro
2002-05-24 20:25 ` Linus Torvalds
2002-05-24 21:15 ` Martin Dalecki [this message]
2002-05-24 22:47 ` Alexander Viro
2002-05-24 22:17 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 0:24 Andries.Brouwer
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=3CEEAD8C.1060202@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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