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: <460FFD0F.7080107@argo.co.il>
Date:	Sun, 01 Apr 2007 21:42:23 +0300
From:	Avi Kivity <avi@...o.co.il>
To:	Davide Libenzi <davidel@...ilserver.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Suparna Bhattacharya <suparna@...ibm.com>,
	Zach Brown <zach.brown@...cle.com>,
	Benjamin LaHaise <bcrl@...ck.org>
Subject: Re: [patch 13/13] signal/timer/event fds v9 - KAIO eventfd support
 example ...

Davide Libenzi wrote:
> On Sun, 1 Apr 2007, Avi Kivity wrote:
>
>   
>> What is the motivation for adding aio_resfd to an individual iocb instead of
>> the entire io context?  It seems redundant, as you can already create multiple
>> io contexts to wait on.
>>     
>
> To add it to the context, you need to either change the context create API 
> (I think no-go here), or add a new syscall just to handle that.
> Doing it in the iocb gives finer grained setup, but can be more work for 
> the user that wants to use it for all the iocbs.
>   

I think it's a bit too fine grained, and a new system call 
(io_bindfd()?) would be easier to use.  In addition, you would move the 
eventfd_fget() out of the submission path.

For the users that want fine grained control, they can already call 
io_setup() multiple times and submit iocbs to different completion rings.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ