linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Murray <mmurray@deepthought.org>
To: linux-ide@vger.kernel.org
Subject: Re: [UPDATED][PATCH 2.6.14]: ide: Enable larger taskfile transfers
Date: Thu, 3 Nov 2005 16:43:55 -0500	[thread overview]
Message-ID: <20051103214355.GA3516@deepthought.org> (raw)
In-Reply-To: <20051102084917.GM26049@suse.de>

Just a few quick questions:

regarding HDIO_DRIVE_TASKFILE:
    I don't see any exact information, however, from what I can infer
from the code, it appears that while the user can specify an
input buffer and/or an output buffer, only one of the buffers would be
filled with useful information. Is it reasonable to assume that
req_task->out_size == 0 req_task->in_size == 0? Or, more specifically,
is it reasonable to return -EINVAL if both are non zero?

    If I were to do zero_copy IO using blk_rq_map_user, should I verify
the user buffer is valid with access_ok() ?

    Why does ide_diag_taskfile() allocate a custom request structure
instead of using blk_get_request(drive->queue, ...) ?

    Given HDIO_DRIVE_TASKFILE, what is the purpose of HDIO_DRIVE_TASK
and HDIO_DRIVE_CMD?

Thank you, Martin

  parent reply	other threads:[~2005-11-03 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 20:24 [UPDATED][PATCH 2.6.14]: ide: Enable larger taskfile transfers Timothy Thelin
2005-11-02  8:49 ` Jens Axboe
2005-11-02 17:23   ` Martin Murray
2005-11-02 19:12     ` Bartlomiej Zolnierkiewicz
2005-11-03 21:43   ` Martin Murray [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 20:42 Timothy Thelin
2005-11-01 19:17 Timothy Thelin
2005-11-01 19:06 Timothy Thelin
2005-11-01 19:27 ` 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=20051103214355.GA3516@deepthought.org \
    --to=mmurray@deepthought.org \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).