linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 19 Jan 2015 08:31:27 -0700	[thread overview]
Message-ID: <54BD234F.3060203@kernel.dk> (raw)
In-Reply-To: <CANP1eJHYUprjvO1o6wfd197LM=Bmhi55YfdGQkPT0DKRn3=q6A@mail.gmail.com>

On 01/19/2015 07:18 AM, Milosz Tanski wrote:
> On Mon, Jan 19, 2015 at 2:34 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
>> On Sun, 2015-01-18 at 23:12 -0800, Jeremy Allison wrote:
>>> On Sun, Jan 18, 2015 at 10:49:36PM -0500, Milosz Tanski wrote:
>>>>
>>>> I have the first version of the FIO cifs support via samba in my fork
>>>> of FIO here: https://github.com/mtanski/fio/tree/samba
>>>>
>>>> Right now it only supports sync mode of FIO (eg. can't submit multiple
>>>> outstanding requests) but I'm looking into how to make it work with
>>>> smb2 read/write calls with the async flag.
>>>>
>>>> Additionally, I'm sure I'm doing some things not quite right in terms
>>>> of smbcli usage as it was a decent amount of trial and error to get it
>>>> to connect (esp. the setup before smbcli_full_connection). Finally, it
>>>> looks like the more complex api I'm using (as opposed to smbclient,
>>>> because I want the async calls) doesn't quite fully export all calls I
>>>> need via headers / public dyn libs so it's a bit of a hack to get it
>>>> to build: https://github.com/mtanski/fio/commit/7fd35359259b409ed023b924cb2758e9efb9950c#diff-1
>>>>
>>>> But it works for my randread tests with zipf and the great part is
>>>> that it should provide a flexible way to test samba with many fake
>>>> clients and access patterns. So... progress.
>>>
>>> One problem here. Looks like fio is under GPLv2-only,
>>> is that correct ?
>>
>> Seems so from the LICENSE file.
>>
>>> If so there's no way to combine the two codebases,
>>> as Samba is under GPLv3-or-later with parts under LGPLv3-or-later.
>>>
>>> fio needs to be GPLv2-or-later in order to be
>>> able to use with libsmbclient.
>>
>> That's one of these pointless licensing complexities that annoy
>> distributions so much ... they're both open source, so there's no real
>> problem except the licence incompatibility. The usual way out of it is
>> just to dual licence the incompatible component.
>>
>> James
>>
>>
>
> Sadly, in this case there's nothing I can do about the license; both
> projects have a right to determine their own licensing. Hopefully, the
> parties can come to some kind of agreement since it would be
> beneficial to use fio to test samba.
>
> This works well enough for me to test test preadv2 using samba and get
> numbers. So I'll use this to do some preadv2 testing using samba for
> different workloads.

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.

So don't worry about licensing for now, just work on improving the 
engine and we'll sort the non-technical details out.

-- 
Jens Axboe


  reply	other threads:[~2015-01-19 15:31 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 [this message]
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
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=54BD234F.3060203@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).