Re: [rfc] direct IO submission and completion scalability issues

David Chinner
2008-02-04T04:41:10Z

On Sun, Feb 03, 2008 at 08:14:45PM -0800, Arjan van de Ven wrote:
> David Chinner wrote:
> >Hi Nick,
> >
> >When Matthew was describing this work at an LCA presentation (not
> >sure whether you were at that presentation or not), Zach came up
> >with the idea that allowing the submitting application control the
> >CPU that the io completion processing was occurring would be a good
> >approach to try. That is, we submit a "completion cookie" with the
> >bio that indicates where we want completion to run, rather than
> >dictating that completion runs on the submission CPU.
> >
> >The reasoning is that only the higher level context really knows
> >what is optimal, and that changes from application to application.
>
> well.. kinda. One of the really hard parts of the submit/completion stuff
> is that
> the slab/slob/slub/slib allocator ends up basically "cycling" memory
> through the system;
> there's a sink of free memory on all the submission cpus and a source of
> free memory
> on the completion cpu. I don't think applications are capable of working
> out what is
> best in this scenario..

Applications as in "anything that calls submit_bio()". i.e, direct I/O,
filesystems, etc. i.e. not userspace but in-kernel applications.

In XFS, simultaneous io completion on multiple CPUs can contribute greatly to
contention of global structures in XFS. By controlling where completions are
delivered, we can greatly reduce this contention, especially on large,
mulitpathed devices that deliver interrupts to multiple CPUs that may be far
distant from each other. We have all the state and intelligence necessary
to control this sort policy decision effectively.....

Cheers,

Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group