From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keith Swett <swettk@gmail.com>
Subject: Re: Trying to track down odd behavior, errors in xen dmesg
Date: Tue, 12 Apr 2011 15:59:48 -0500
Message-ID: <BANLkTikiWVXgvANu2RAph6m5T5i4_aE7Hw@mail.gmail.com>
References: <BANLkTimAO=X_-o2haJmsgaA-DdBgijQ8tQ@mail.gmail.com>
	<20110407160139.GA9826@dumpdata.com>
	<BANLkTi=kaTPqPjw_QkaLoLd_-Rx7Y4t7bw@mail.gmail.com>
	<20110407162307.GA30422@dumpdata.com>
	<BANLkTim_Khsw=KCvHFqg1mzwQGtayQLRpQ@mail.gmail.com>
	<BANLkTi==g14Na0XCBAC0zqOZ_xFU16YSCQ@mail.gmail.com>
	<20110408135337.GG6189@dumpdata.com>
	<BANLkTinJ4eu6TFhTujbdW_JUJ_4ZVQ3hQQ@mail.gmail.com>
	<20110412102002.GA30108@dumpdata.com>
	<BANLkTi=p3h7jyxpZhkbect25tPngFf5Xiw@mail.gmail.com>
	<20110412204123.GA7308@dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20110412204123.GA7308@dumpdata.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Konrad,

I'm not seeing the kernel messages, so i'm wondering if something else
changed, and if I applied the patch correctly.
Trying to repeat the process from this morning with a clean tree to confirm=
.


--Keith


On Tue, Apr 12, 2011 at 3:41 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, Apr 12, 2011 at 11:20:07AM -0500, Keith Swett wrote:
>> Konrad,
>>
>> That seems to have fixed it, i'm not seeing the error messages anymore
>> and performance seems correct thus far. =A0I'll continue to test a
>> couple more scenarios today and let you know if I see anything odd.
>
> OK. It might take a bit of time. You should see some kernel logs when
> it detects the iSCSI retransmission errors. Why don't we let this
> run for a week or so to make sure it does not cause regressions.
>
>> How should we go about getting this over to the debian maintainers?
>
> Lets make sure it does not break anything.
>>
>> --Keith
>>
>> On Tue, Apr 12, 2011 at 5:20 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> > On Fri, Apr 08, 2011 at 08:59:58AM -0500, Keith Swett wrote:
>> >> Not a problem, would be happy to beta test. =A0Send the patches my wa=
y
>> >> whenever they're available.
>> >
>> > Did a backport, but I don't have yet the software iSCSI target
>> > available so couldn't do proper tests. Please test and email kernel lo=
g
>> > messages.
>> >
>> >> Would you like me to be building against the debian-src of the
>> >> packages or would another tree be more beneficial?
>> >
>> > That tree should be OK.
>> >
>> > See attached patch.
>> >
>