mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Muhammad Mutahir Latif" <mutahirlatif@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: SATA passthrough commands from User Space
Date: Mon, 15 Dec 2008 18:55:31 +0500	[thread overview]
Message-ID: <14cd75110812150555m36e1fef8w8f966b9acdd336@mail.gmail.com> (raw)
In-Reply-To: <4940CFB3.8030005@garzik.org>

Thank you Jeff for the SG_IO suggestion. Are there any numbers as to
the average throughput achieved using the SG_IO ioctl. The reason I am
asking is that for our scenario the data transfer throughput required
might not be fulfilled using the SG_IO ioctl due to the SCSI->ATA
translations. In case the SG_IO does not fulfill the requirement,
where should we add IOCTL functionality. At first I was thinking of
adding it to the AHCI driver, but by looking at the code I saw that
the ahci driver only implements functions so that they can be hooked
with the libata framework, so  should I add IOCTL hooks to the
libata?. Please let me know if I am by any chance going completely in
the wrong direction.

Thanks

Mutahir

On Thu, Dec 11, 2008 at 1:30 PM, Jeff Garzik <jeff@garzik.org> wrote:
> Muhammad Mutahir Latif wrote:
>>
>> Hi
>>
>> I am new to linux kernel development and need help in developing an
>> application in linux for a SATA device. What is required is that the
>> application needs to send raw SATA commands along with data (like Read
>> DMA, Write FPDMA etc) to a SATA hard disk. Secondly we also have to
>> achieve a reasonably high data transfer throughput.
>
> Use the existing SG_IO ioctl.
>
>        Jeff
>
>
>
>

      reply	other threads:[~2008-12-15 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  8:05 Muhammad Mutahir Latif
2008-12-11  8:30 ` Jeff Garzik
2008-12-15 13:55   ` Muhammad Mutahir Latif [this message]

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=14cd75110812150555m36e1fef8w8f966b9acdd336@mail.gmail.com \
    --to=mutahirlatif@gmail.com \
    --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

all inboxes | Powered by JetHome®