linux-kernel - Re: Queuing multiple task

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] [day] [month] [year] [list]

Message-ID: <20111004114314.45d8ac5f@lxorguk.ukuu.org.uk>
Date:	Tue, 4 Oct 2011 11:43:14 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ganesh Karuppur Rajagopalan <ganesh.kr356@...il.com>
Cc:	linux-kernel@...r.kernel.org, Pallav Bose <pallavbose@...il.com>
Subject: Re: Queuing multiple task_struct structures?

> thread which uses the ioctl() system call to send a userspace buffer
> to my block device driver. Once I queue up multiple task_structs, I
> would like to keep them on the queue until a particular condition is
> met (i.e., the buffer has been written down to the disk).

We already have a perfectly usable raw I/O interface set, why not just
use those ?

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/