From: Jens Axboe <axboe@kernel.dk>
To: Jeremy Allison <jra@samba.org>
Cc: Steve French <smfrench@gmail.com>,
Milosz Tanski <milosz@adfin.com>,
Volker Lendecke <Volker.Lendecke@sernet.de>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
linux-mm <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] async buffered diskio read for userspace apps
Date: Sat, 24 Jan 2015 16:00:44 -0700 [thread overview]
Message-ID: <54C4241C.9070406@kernel.dk> (raw)
In-Reply-To: <20150124055352.GE6636@jeremy-HP>
On 01/23/2015 10:53 PM, Jeremy Allison wrote:
> On Fri, Jan 23, 2015 at 07:17:05PM -0700, Jens Axboe wrote:
>> On 01/23/2015 04:15 PM, Steve French wrote:
>>> On Mon, Jan 19, 2015 at 10:20 AM, Milosz Tanski <milosz@adfin.com> wrote:
>>>> On Mon, Jan 19, 2015 at 11:10 AM, Volker Lendecke
>>>> <Volker.Lendecke@sernet.de> wrote:
>>>>> On Mon, Jan 19, 2015 at 08:31:27AM -0700, 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.
>>>>>
>>>>> The published libsmbclient API misses the async features
>>>>> that are needed here. Milosz needs to go lower-level.
>>>>>
>>>>> Volker
>>>>
>>>> Volker, the sync code path works; in fact I pushed some minor
>>>> corrections to my branch this morning. And for now using FIO I can
>>>> generate multiple clients (threads / processes).
>>>>
>>>> I started working on the async features (SMB2 async read/write) for
>>>> client library the samba repo. There's a patch there for the first
>>>> step of it it there; see the other email I sent to you and Jeremy. I
>>>> was going to make sure it licensed under whatever it needs to get into
>>>> the samba repo... and since this is done on my own time I personally
>>>> don't care what license it's under provided it's not a PITA.
>>>
>>> Why not do the async read/write via the kernel client if the license
>>> is an issue? It already has async SMB2/SMB3 operations
>>> (with a synchronous send/receive-like wrapper).
>>
>> The license issue has been solved. Fio is cross platform, so would
>> be preferable to have this work through libsmbclient, if at all
>> possible.
>
> How did the license issue get solved ? Did I miss some email
> on that ?
Only the cifs engine is linked with libsmbclient, so that particular
engine can be licensed as v2 or later (or v3, u to Milosz).
--
Jens Axboe
next prev parent reply other threads:[~2015-01-24 23:00 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 [this message]
2015-01-20 19:33 ` Jens Axboe
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=54C4241C.9070406@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 \
--cc=smfrench@gmail.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).