<bart.vanass...@sandisk.com> wrote:
> On 09/01/2016 02:48 PM, Alex Austin wrote:
>>
>> CC'ing linux-scsi and linux-block.
>>
>> Also, please CC me in replies.
>>
>> On Thu, Sep 1, 2016 at 4:43 PM, Alex Austin <aaus...@oceantechonline.com>
>>
:
> On 09/01/2016 02:48 PM, Alex Austin wrote:
>>
>> CC'ing linux-scsi and linux-block.
>>
>> Also, please CC me in replies.
>>
>> On Thu, Sep 1, 2016 at 4:43 PM, Alex Austin
>> wrote:
>>>
>>> Hello,
>>> What is the most perfor
CC'ing linux-scsi and linux-block.
Also, please CC me in replies.
On Thu, Sep 1, 2016 at 4:43 PM, Alex Austin <aaus...@oceantechonline.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
CC'ing linux-scsi and linux-block.
Also, please CC me in replies.
On Thu, Sep 1, 2016 at 4:43 PM, Alex Austin 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
), 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
), 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
6 matches
Mail list logo