From: Jens Axboe <axboe@kernel.dk>
To: Milosz Tanski <milosz@adfin.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Jeremy Allison <jra@samba.org>,
Volker Lendecke <Volker.Lendecke@sernet.de>,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] async buffered diskio read for userspace apps
Date: Tue, 20 Jan 2015 12:33:22 -0700 [thread overview]
Message-ID: <54BEAD82.3070501@kernel.dk> (raw)
In-Reply-To: <54BD234F.3060203@kernel.dk>
On 01/19/2015 08:31 AM, Jens Axboe wrote:
> I didn't look at your code yet, but I'm assuming it's a self contained
> IO engine. So we should be able to make that work, by only linking the
> engine itself against libsmbclient. But sheesh, what a pain in the butt,
> why can't we just all be friends.
I pulled it in for testing, and came up with this patch [1]. If you
don't do anything, it'll build cifs into fio as before. If you add
--cifs-external to the configure arguments, it'll build cifs.so as an
externally loadable module. You'd then use:
ioengine=/path/to/cifs.so
to use that module. I did not add an install target, I'll leave that to
distros...
Let me know how that works for you. And let me know how far along you
are with the cifs engine, I'd like to pull it in.
http://git.kernel.dk/?p=fio.git;a=shortlog;h=refs/heads/cifs
[1]
http://git.kernel.dk/?p=fio.git;a=commit;h=c2c05e33b753ae686e24b43d1034d0c474203729
--
Jens Axboe
next prev parent reply other threads:[~2015-01-20 19:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 17:43 [LSF/MM TOPIC] async buffered diskio read for userspace apps Milosz Tanski
2015-01-15 18:30 ` Jeff Moyer
2015-01-16 15:40 ` Milosz Tanski
2015-01-15 22:31 ` [Lsf-pc] " Jan Kara
2015-01-16 15:44 ` Milosz Tanski
2015-01-16 16:55 ` Jeremy Allison
2015-01-19 3:49 ` Milosz Tanski
2015-01-19 7:12 ` Jeremy Allison
2015-01-19 7:34 ` James Bottomley
2015-01-19 14:18 ` Milosz Tanski
2015-01-19 15:31 ` Jens Axboe
2015-01-19 15:49 ` James Bottomley
2015-01-19 16:48 ` Jeremy Allison
2015-01-19 17:26 ` James Bottomley
2015-01-19 17:32 ` Jeremy Allison
2015-01-19 17:36 ` Richard Sharpe
2015-01-19 20:00 ` Jens Axboe
2015-01-19 16:10 ` Volker Lendecke
2015-01-19 16:20 ` Milosz Tanski
2015-01-19 16:50 ` Jeremy Allison
2015-01-23 23:15 ` Steve French
2015-01-24 2:17 ` Jens Axboe
2015-01-24 5:53 ` Jeremy Allison
2015-01-24 23:00 ` Jens Axboe
2015-01-20 19:33 ` Jens Axboe [this message]
2015-01-20 23:07 ` Milosz Tanski
2015-01-20 23:22 ` Milosz Tanski
2015-01-20 23:26 ` Jens Axboe
2015-01-20 23:30 ` Jens Axboe
2015-01-20 23:53 ` Milosz Tanski
2015-01-21 21:17 ` Jens Axboe
2015-01-23 0:03 ` Milosz Tanski
2015-01-23 0:10 ` Milosz Tanski
2015-01-19 17:04 ` Jeremy Allison
2015-01-19 17:18 ` Richard Sharpe
2015-01-19 17:20 ` Jeremy Allison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BEAD82.3070501@kernel.dk \
--to=axboe@kernel.dk \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Volker.Lendecke@sernet.de \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jra@samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=milosz@adfin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).