On 15-1-2016 11:52, Willem Jan Withagen wrote:
On 30-11-2015 14:21, Sage Weil wrote:
The problem with all of the porting code in general is that it is doomed
to break later on if we don't have (at least) ongoing build tests. In
order for a FreeBSD or OSX port to continue working we need VMs that run
either gitbuilder or a jenkins job or similar so that we can tell when it
breaks.
If someone is willing to run a VM somewhere to do this we can pretty
easily stick it on the gitbuilder page at
http://ceph.com/gitbuilder.cgi
Well this is real nice case of such an incident.
I'm verifying my changes to the C/C++ code, after having forwarded to HEAD.
And now I get bluestore complaining that it requires AIO.
Something I've thusfar excluded in the build.
Does Bluestore really require AIO??
FreeBSD does have AIO, but to take simple steps one at the time, I
excluded it
with configure. Mainly because it bombs at compile time. Probably due to
different include files, or function nameing.....
So, in order of preference:
- Can I disable AIO for Bluestore
- Can I disable bluestore being build?
Spoke a bit too soon.
FreeBSD has AIO, loadable as kernelmodule. with the following systemcalls.
aio_cancel(2), aio_error(2), aio_read(2), aio_return(2), aio_suspend(2),
aio_waitcomplete(2), aio_write(2), lio_listio(2)
But libaio is based on:
/* Actual syscalls */
extern int io_setup(int maxevents, io_context_t *ctxp);
extern int io_destroy(io_context_t ctx);
extern int io_submit(io_context_t ctx, long nr, struct iocb *ios[]);
extern int io_cancel(io_context_t ctx, struct iocb *iocb, struct
io_event *evt);
extern int io_getevents(io_context_t ctx_id, long min_nr, long nr,
struct io_event *events, struct timespec *timeout);
So glueing that together is not just fixing some include files, and or
fetching
some shim-library that is lurking out in /usr/ports...
And for the time being I would like to skip over the libaio hurdle.
Is that possible?
--WjW
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
