After seeing original commit from James, this patch looks OK to me. Please consider this patch as ACKed by me. Thanks, Kashyap -----Original Message----- From: Vitaly Bordug [mailto:vitb@xxxxxxxxxxxxxxxxxxx] Sent: Monday, September 07, 2009 7:16 PM To: Desai, Kashyap Cc: Moore, Eric; DL-MPT Fusion Linux; linux-scsi@xxxxxxxxxxxxxxx Subject: Re: [PATCH] mptsas: fix dma alignment В Mon, 7 Sep 2009 16:42:54 +0530 "Desai, Kashyap" <Kashyap.Desai@xxxxxxx> пишет: > Can you send an exact link for "465ff.. commit"? > Sure, http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=465ff3185e0cb76d46137335a4d21d0d9d3ac8a2 > Thanks, > Kashyap > > -----Original Message----- > From: Vitaly Bordug [mailto:vitb@xxxxxxxxxxxxxxxxxxx] > Sent: Wednesday, September 02, 2009 2:34 AM > To: Moore, Eric > Cc: DL-MPT Fusion Linux; linux-scsi@xxxxxxxxxxxxxxx > Subject: [PATCH] mptsas: fix dma alignment > > > From: Yuri Tikhonov <yur@xxxxxxxxxxx> > > fusion mptsas: fix dma alignment > > Since the 465ff.. commit from James Bottomley relaxes the default > SCSI DMA alignment from 512 bytes to 4 bytes, then, in the mptsas > driver, we should explicitly set the alignment to the workable > 512 bytes value. > > Signed-off-by: Ilya Yanok <yanok@xxxxxxxxxxx> > Signed-off-by: Yuri Tikhonov <yur@xxxxxxxxxxx> > Signed-off-by: Sergei Poselenov <sposelenov@xxxxxxxxxxx> > Signed-off-by: Vitaly Bordug <vitb@xxxxxxxxxxxxxxxxxxx> > --- > > drivers/message/fusion/mptsas.c | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > > diff --git a/drivers/message/fusion/mptsas.c > b/drivers/message/fusion/mptsas.c index 55ff252..2334f26 100644 > --- a/drivers/message/fusion/mptsas.c > +++ b/drivers/message/fusion/mptsas.c > @@ -1843,6 +1843,7 @@ mptsas_slave_alloc(struct scsi_device *sdev) > return -ENXIO; > > out: > + blk_queue_update_dma_alignment(sdev->request_queue, 511); > vdevice->vtarget->num_luns++; > sdev->hostdata = vdevice; > return 0; -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
