linux-kernel - Re: Block-level access

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGA4w7=eM9+sHMNaCXx5tXCEEyeJp0wb7ZqpAiuW35u+PEiSBw@mail.gmail.com>
Date:   Thu, 1 Sep 2016 16:48:28 -0500
From:   Alex Austin <aaustin@...antechonline.com>
To:     linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
        linux-block@...r.kernel.org
Subject: Re: Block-level access

CC'ing linux-scsi and linux-block.

Also, please CC me in replies.

On Thu, Sep 1, 2016 at 4:43 PM, Alex Austin <aaustin@...antechonline.com> wrote:
> Hello,
> What is the most performant way to directly interface with an attached hard
> drive? I've so far used read()/write() on /dev/sd_ but I find error handling
> exceedingly difficult, as I don't always even get errors reported, even if the
> open() call includes O_DIRECT. I've also used ioctl(SG_IO), but find that it's
> extremely slow due to the lack of queuing support in the API. Is there a
> mid-level API that will get me decent error handling while allowing command
> queuing, or do I just need to make multiple threads all doing separate SG_IO
> ioctls?
>
> Thank you,
> - Alex Austin
>
> --
> Intelligence is knowing that a tomato is a fruit; wisdom is knowing that it
> doesn't go in a fruit salad; charisma is selling a tomato-based fruit salad.



-- 
Intelligence is knowing that a tomoato is a fruit; wisdom is knowing
that it doesn't go in a fruit salad; charisma is selling a
tomato-based fruit salad.