From: Jeremy Allison <jra@samba.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jens Axboe <axboe@kernel.dk>, Milosz Tanski <milosz@adfin.com>,
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, Jeremy Allison <jra@samba.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] async buffered diskio read for userspace apps
Date: Mon, 19 Jan 2015 08:48:57 -0800 [thread overview]
Message-ID: <20150119164857.GC12308@jeremy-HP> (raw)
In-Reply-To: <1421682581.2080.22.camel@HansenPartnership.com>
On Mon, Jan 19, 2015 at 07:49:41AM -0800, James Bottomley wrote:
>
> For fio, it likely doesn't matter. Most people download the repository
> and compile it themselves when building the tool. In that case, there's
> no licence violation anyway (all GPL issues, including technical licence
> incompatibility, manifest on distribution not on use). It is a problem
> for the distributors, but they're well used to these type of self
> inflicted wounds.
That's true, but it is setting a bear-trap for distributors.
Might be better to keep the code repositories separate so at
lease people have a *chance* of noticing there's a problem
here.
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Allison <jra@samba.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jens Axboe <axboe@kernel.dk>, Milosz Tanski <milosz@adfin.com>,
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, Jeremy Allison <jra@samba.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] async buffered diskio read for userspace apps
Date: Mon, 19 Jan 2015 08:48:57 -0800 [thread overview]
Message-ID: <20150119164857.GC12308@jeremy-HP> (raw)
In-Reply-To: <1421682581.2080.22.camel@HansenPartnership.com>
On Mon, Jan 19, 2015 at 07:49:41AM -0800, James Bottomley wrote:
>
> For fio, it likely doesn't matter. Most people download the repository
> and compile it themselves when building the tool. In that case, there's
> no licence violation anyway (all GPL issues, including technical licence
> incompatibility, manifest on distribution not on use). It is a problem
> for the distributors, but they're well used to these type of self
> inflicted wounds.
That's true, but it is setting a bear-trap for distributors.
Might be better to keep the code repositories separate so at
lease people have a *chance* of noticing there's a problem
here.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-01-19 16:48 UTC|newest]
Thread overview: 59+ 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-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-16 16:55 ` Jeremy Allison
2015-01-19 3:49 ` Milosz Tanski
2015-01-19 7:12 ` Jeremy Allison
2015-01-19 7:12 ` Jeremy Allison
2015-01-19 7:34 ` James Bottomley
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:31 ` Jens Axboe
2015-01-19 15:49 ` James Bottomley
2015-01-19 15:49 ` James Bottomley
2015-01-19 16:48 ` Jeremy Allison [this message]
2015-01-19 16:48 ` Jeremy Allison
2015-01-19 17:26 ` James Bottomley
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 20:00 ` Jens Axboe
2015-01-19 16:10 ` Volker Lendecke
2015-01-19 16:10 ` Volker Lendecke
2015-01-19 16:20 ` Milosz Tanski
2015-01-19 16:20 ` Milosz Tanski
2015-01-19 16:50 ` Jeremy Allison
2015-01-19 16:50 ` Jeremy Allison
2015-01-23 23:15 ` Steve French
2015-01-23 23:15 ` Steve French
2015-01-24 2:17 ` Jens Axboe
2015-01-24 2:17 ` Jens Axboe
2015-01-24 5:53 ` Jeremy Allison
2015-01-24 5:53 ` Jeremy Allison
2015-01-24 23:00 ` Jens Axboe
2015-01-24 23:00 ` Jens Axboe
2015-01-20 19:33 ` Jens Axboe
2015-01-20 19:33 ` Jens Axboe
2015-01-20 23:07 ` Milosz Tanski
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:26 ` Jens Axboe
2015-01-20 23:30 ` Jens Axboe
2015-01-20 23:30 ` Jens Axboe
2015-01-20 23:53 ` Milosz Tanski
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:04 ` Jeremy Allison
2015-01-19 17:18 ` Richard Sharpe
2015-01-19 17:20 ` Jeremy Allison
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=20150119164857.GC12308@jeremy-HP \
--to=jra@samba.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Volker.Lendecke@sernet.de \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.