From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: linux-iscsi-target-dev@googlegroups.com
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Christoph Hellwig" <hch@infradead.org>,
"FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Mike Christie" <michaelc@cs.wisc.edu>,
"Hannes Reinecke" <hare@suse.de>,
"Jens Axboe" <jens.axboe@oracle.com>,
"Vladislav Bolkhovitin" <vst@vlnb.net>
Subject: Re: [Announce]: Target_Core_Mod/ConfigFS and LIO-Target v3.0 work
Date: Sat, 13 Dec 2008 12:56:35 +0100 [thread overview]
Message-ID: <e2e108260812130356y1fe60713xf844a35c775e161d@mail.gmail.com> (raw)
In-Reply-To: <1229167118.4153.930.camel@haakon2.linux-iscsi.org>
On Sat, Dec 13, 2008 at 12:18 PM, Nicholas A. Bellinger
<nab@linux-iscsi.org> wrote:
> Of course I fix bugs when people report them.
Things have changed then since the beginning of this year. As anyone
can see in the threads I referred to, you have done your best to deny
that the crashes and system hangs were caused by LIO, although I had
posted exact instructions on how to reproduce the bugs. Regarding
kernel integration and subsystem maintainership: one of the important
tasks of a maintainer is to verify whether reported bugs are
reproducible, and if so, to resolve them. I'm happy none of the
current kernel maintainers has the habitude of denying bug reports
that are 100% reproducible and which contain exact instructions about
how to reproduce the bug.
> "Zero-copy means that data is copied as few times as possible".
>
> when I was attempting to explain the finer pointers of
> Target_Core_Mod/ConfigFS design to you and Vlad. Remember that one..?
>
> http://groups.google.com/group/linux-iscsi-target-dev/browse_thread/thread/8cff61671cd2de6b/37ade00e607dd8c8
You are going off topic -- the above statement has nothing to do with
this thread.
Regarding the statement itself: it's incorrect to quote that sentence
out of its context. In that thread, as anyone can see who looks up the
URL, I was using the word copies to refer to transfers between
hardware and RAM, not to copying data from RAM to RAM. Looking at that
statement now I agree that that was misleading, and that I should have
written that statement in another way.
Do you think people like it to discuss with you when you try to make
them appear ridiculous all the time ?
And what I do not understand is that you are playing games with the CC
list all of the time. It's considered impolite to leave out people
from a CC list unless someone asked explicitly to be left out.
Bart.
next prev parent reply other threads:[~2008-12-13 11:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 3:14 Nicholas A. Bellinger
2008-12-11 19:24 ` Bart Van Assche
2008-12-11 19:58 ` Nicholas A. Bellinger
2008-12-12 7:21 ` Bart Van Assche
2008-12-12 9:40 ` Nicholas A. Bellinger
2008-12-13 6:20 ` Valdis.Kletnieks
2008-12-13 8:27 ` Nicholas A. Bellinger
2008-12-13 9:41 ` Bart Van Assche
2008-12-13 10:08 ` Nicholas A. Bellinger
2008-12-13 10:23 ` Bart Van Assche
2008-12-13 11:18 ` Nicholas A. Bellinger
2008-12-13 11:56 ` Bart Van Assche [this message]
2008-12-13 12:33 ` Nicholas A. Bellinger
[not found] ` <e2e108260812130450y3288b32av7f435544823d9e97@mail.gmail.com>
2008-12-13 13:14 ` Nicholas A. Bellinger
2008-12-13 15:24 ` James Bottomley
2008-12-13 22:50 ` Nicholas A. Bellinger
2008-12-14 16:53 ` Bart Van Assche
2008-12-16 18:45 ` Vladislav Bolkhovitin
2008-12-13 15:35 ` Vladislav Bolkhovitin
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=e2e108260812130356y1fe60713xf844a35c775e161d@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jens.axboe@oracle.com \
--cc=linux-iscsi-target-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=vst@vlnb.net \
/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
all inboxes | Powered by JetHome®