Hi
On Sun, 24 Feb 2008, Andrew Morton wrote:
Hi Andrew,
thanks a lot for reply, I'm attaching requested information.
please let me know if You need more information/testing, whatever.
I'll be glad to help.
BR
nik
Areca support doesn't seem to be very interested in the problem :-(
(cc's added
Hi Nikola,
As I said, we will test on our site.
Our support team will help you to settle the issue.
Sorry for your inconvenience,
-Original Message-
From: Nikola Ciprich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26, 2008 5:36 PM
To: Andrew Morton
Cc: [EMAIL PROTECTED]; linux-scsi@
On Mon, Feb 25, 2008 at 11:40:35PM +0100, Andi Kleen wrote:
> On Mon, Feb 25, 2008 at 02:47:46PM -0700, Matthew Wilcox wrote:
> > I have to say I really don't like this patch. I'll look up my current
>
> Why do you not like it? What would you do better?
>
> > patch queue for this driver next wee
Hi James,
Le Thu, 14 Feb 2008 09:50:58 -0600,
James Bottomley <[EMAIL PROTECTED]> a écrit :
> Yes, it's already on its way to stable. The process requires the fix
> to be committed upstream first. There's an automated script that
> sends these commits back to stable once they're upstream (provi
On Tue, 2008-02-26 at 04:44 +0100, Andi Kleen wrote:
> On Mon, Feb 25, 2008 at 03:50:22PM -0700, Matthew Wilcox wrote:
> > On Mon, Feb 25, 2008 at 11:40:35PM +0100, Andi Kleen wrote:
> > > > (I must have fixed it somehow because it works on parisc, which is most
> > > > unforgiving of drivers which
On Tue, 2008-02-26 at 12:29 +0800, nickcheng wrote:
> James,
> Appreciate for your answer.
> One more question: do you think there are any compatibility issues on
> kmalloc/kfree pair?
> I just trace the kernel code. It looks like it would not.
> But I am not quite sure absolutely.
> May I have you
On Tue, 26 Feb 2008 10:35:31 +0100 (CET) Nikola Ciprich <[EMAIL PROTECTED]>
wrote:
> Hi
>
> On Sun, 24 Feb 2008, Andrew Morton wrote:
>
> Hi Andrew,
> thanks a lot for reply, I'm attaching requested information.
> please let me know if You need more information/testing, whatever.
> I'll be glad
Hello Andre,
On Tuesday 26 February 2008 18:43:14 Andre Noll wrote:
> Hi
>
> we are experiencing massive performance problems with two of our
> Linux servers that contain 3ware controllers on a Tyan mainboard and
> a couple of 1T disks.
>
> During the daily cron job that uses rsync to sync a 500G
[EMAIL PROTECTED] wrote on Mon, 25 Feb 2008 15:02 -0800:
> Ugh.
[pw wrote:]
> > Looking at the FMR dirty list unmapping code in
> > ib_fmr_batch_release(), there is a section that pulls all the dirty
> > entries onto a list that it will later unmap and put back on the
> > free list.
>
> > But
This reverts commit a3cd7d9070be417a21905c997ee32d756d999b38.
The original commit breaks iSER reliably, making it complain:
iser: iser_reg_page_vec:ib_fmr_pool_map_phys failed: -11
The FMR cleanup thread runs ib_fmr_batch_release() as dirty
entries build up. This commit causes clean but use
Commit a3cd7d9070be417a21905c997ee32d756d999b38 (IB/fmr_pool:
ib_fmr_pool_flush() should flush all dirty FMRs) caused a
regression for iSER and was reverted in
e5507736c6449b3253347eed6f8ea77a28cf688e.
This change attempts to redo the original patch so that all used
FMR entries are flushed when ib
Andre Noll wrote:
we are experiencing massive performance problems with two of our
Linux servers that contain 3ware controllers on a Tyan mainboard and
a couple of 1T disks.
During the daily cron job that uses rsync to sync a 500G file system
from another machine to the raid on the 3ware control
From: Mike Christie <[EMAIL PROTECTED]>
The old tools did not set max session cmds. This is a regression.
I removed the check when merging the power of 2 patch.
Signed-off-by: Mike Christie <[EMAIL PROTECTED]>
---
drivers/scsi/libiscsi.c |4 ++--
drivers/scsi/scsi_transport_iscsi
On Tue, Feb 26, 2008 at 07:18:18AM -0800, James Bottomley wrote:
> On Tue, 2008-02-26 at 04:44 +0100, Andi Kleen wrote:
> > No pci_alloc_coherent works, but pci_map_* will not.
>
> Yes, it does ... dma_map is a flush/virt_to_phys on x86. so of course it
> works. If you mean it doesn't transform f
Pete, the subject says "PATCH 1/2" but I didn't see any follow-up message
for PATCH 2/2. Just wondering :)
Benny
On Feb. 26, 2008, 10:27 -0800, Pete Wyckoff <[EMAIL PROTECTED]> wrote:
> This reverts commit a3cd7d9070be417a21905c997ee32d756d999b38.
>
> The original commit breaks iSER reliably, ma
Hi Andrew,
no, right now I have the machine in the weird state, swap is empty (3GB),
and so is bigger part of RAM (~100MB free), and the gcc crashes even when
trying to compile c program with empty main function. so it doesn't seem
to be problem with memory exhaustion.
Hopefully the areca guys
On Tue, Feb 26, 2008 at 11:23:01AM -0800, Benny Halevy wrote:
> Pete, the subject says "PATCH 1/2" but I didn't see any follow-up message
> for PATCH 2/2. Just wondering :)
I think the problem's on your end ... I got it and so did marc:
http://marc.info/?l=linux-scsi&m=120405067313933&w=2
--
Int
Diabolical ;-)
Thanks for the pointer!
Benny
On Feb. 26, 2008, 11:39 -0800, Matthew Wilcox <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 26, 2008 at 11:23:01AM -0800, Benny Halevy wrote:
>> Pete, the subject says "PATCH 1/2" but I didn't see any follow-up message
>> for PATCH 2/2. Just wondering :)
>
This looks like a really nice approach to me. Olaf?
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
19 matches
Mail list logo
