Hey- this is great stuff. This means I can finally give up on my stuff
for linux now that there's some better and more integral stuff in
place. Woo Hoo!
On 10/23/07, Seokmann Ju <[EMAIL PROTECTED]> wrote:
> Thayumanavar Sachithanantham wrote:
> > Hi All,
> >
> > Does the recent target mode support
Hi Seokmann,
Thanks and nice to know that we would having target mode support for
QLA24xx series.
I could help out in supporting target mode for qla24xx by doing some
preliminary testing as i have a QLA2462 test setup.
Thanks,
Thayumanavar S.
-
To unsubscribe from this list: send the line "unsubs
On Tue, 23 Oct 2007 07:48:30 -0700
Seokmann Ju <[EMAIL PROTECTED]> wrote:
> FUJITA Tomonori wrote:
> > On Tue, 23 Oct 2007 13:47:20 +0530
> > "Thayumanavar Sachithanantham" <[EMAIL PROTECTED]> wrote:
> >
> >> Hi All,
> >>
> >> Does the recent target mode support added for tgt support target mode
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Tue, 23 Oct 2007 18:06:51 -0400
> James Bottomley wrote:
> > On Tue, 2007-10-23 at 17:09 -0400, Jeff Garzik wrote:
> >> James Bottomley wrote:
> >>> This should be the final SCSI updates; it's mainly just a few accessor
> >>> completion updates and two d
PATCH 1 of 1
This patch updates the copyright information for the cciss driver. It
includes extending the year to 2007 (how timely) and some minor corrections
deemed necessary by HP legal and the Open Source Review Board. Please
consider this patch for inclusion.
Signed-off-by: Mike Miller <[EMAI
James Bottomley wrote:
On Tue, 2007-10-23 at 17:09 -0400, Jeff Garzik wrote:
James Bottomley wrote:
This should be the final SCSI updates; it's mainly just a few accessor
completion updates and two driver merges (sym2 and qla2xxx) we also
secured DaveM's agreement to remove fcal/fc4, which expl
On Tue, 2007-10-23 at 17:09 -0400, Jeff Garzik wrote:
> James Bottomley wrote:
> > This should be the final SCSI updates; it's mainly just a few accessor
> > completion updates and two driver merges (sym2 and qla2xxx) we also
> > secured DaveM's agreement to remove fcal/fc4, which explains the high
On Mon, Oct 22, 2007 at 07:09:56PM -0700, Linus Torvalds wrote:
> Umm. This is why we write things like
>
> static void double_lock_balance(struct rq *this_rq, struct rq *busiest)
> __releases(this_rq->lock)
> __acquires(busiest->lock)
> __acquires(t
James Bottomley wrote:
This should be the final SCSI updates; it's mainly just a few accessor
completion updates and two driver merges (sym2 and qla2xxx) we also
secured DaveM's agreement to remove fcal/fc4, which explains the high
removal line count.
The patch is available here:
master.kernel.
This should be the final SCSI updates; it's mainly just a few accessor
completion updates and two driver merges (sym2 and qla2xxx) we also
secured DaveM's agreement to remove fcal/fc4, which explains the high
removal line count.
The patch is available here:
master.kernel.org:/pub/scm/linux/kernel
On Fri, Oct 19, 2007 at 12:33:31PM -0600, Matthew Wilcox wrote:
>
> This fairly naive patch introduces alloc_cmnd and destroy_cmnd. I'm not
> exactly happy about passing down the gfp_mask -- I'd prefer to be able
> to allocate scsi_cmnds before we grab the queue_lock (and hence get
> rid of the p
Hi all,
I have 44 supermicro PDSMi servers running linux 2.6.17.13.
Each of these systems have a Promise Super Trak EX16350 controller with 16 WDC
WD5000ABYS-01TNA disks connected.
The controllers have BIOS 2.9.022 installed and the stex driver used is
version 2.9.0.16.
These servers are used in
On Tue, Oct 23 2007 at 21:15 +0200, Matthew Wilcox <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 23, 2007 at 08:46:52PM +0200, Boaz Harrosh wrote:
>>> We could also add an alloc_bidi_cmnd/destroy_bidi_cmnd to the shost
>>> template. Presumably most commands won't be bidi for any given host,
>>> so it'd
On Tue, Oct 23, 2007 at 11:48:04AM -0600, Matthew Wilcox wrote:
> On Tue, Oct 23, 2007 at 06:49:17PM +0200, Boaz Harrosh wrote:
> > You know Matthew when you first talked about this, I envisioned
> > something else.
>
> Right, so did I. Christoph felt that alloc_cmnd/destroy_cmnd a la the
> VFS l
On Tue, Oct 23, 2007 at 08:46:52PM +0200, Boaz Harrosh wrote:
> > We could also add an alloc_bidi_cmnd/destroy_bidi_cmnd to the shost
> > template. Presumably most commands won't be bidi for any given host,
> > so it'd be a waste of space to allocate them for all commands.
>
> Well no one really
On Tue, Oct 23 2007 at 19:48 +0200, Matthew Wilcox <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 23, 2007 at 06:49:17PM +0200, Boaz Harrosh wrote:
>> You know Matthew when you first talked about this, I envisioned
>> something else.
>
> Right, so did I. Christoph felt that alloc_cmnd/destroy_cmnd a la
On Tue, Oct 23, 2007 at 06:49:17PM +0200, Boaz Harrosh wrote:
> You know Matthew when you first talked about this, I envisioned
> something else.
Right, so did I. Christoph felt that alloc_cmnd/destroy_cmnd a la the
VFS layer's alloc_inode/destroy_inode was a better route. I didn't have
a strong
Matthew Wilcox wrote:
On Mon, Oct 22, 2007 at 10:33:41AM -0600, Moore, Eric wrote:
On Monday, October 22, 2007 10:18 AM, Matthew Wilcox wrote:
Sounds like we need a new driver written to support the FC909 then.
Unless we could pretend the FC909 is a parallel scsi card or something
... that was
Hello Tejun,
On Tuesday 23 October 2007 10:08:01 Tejun Heo wrote:
> Jeff Garzik wrote:
> > Alan Cox wrote:
> >>> 2) Once we identified, over time, the set of drives affected by this
> >>> 3112 quirk (aka drives that didn't fully comply to SATA spec), the
> >>> debugging of corruption cases largely
On Mon, 2007-10-22 at 13:57 +0200, Hannes Reinecke wrote:
> Matthew Wilcox wrote:
> > On Mon, Oct 22, 2007 at 08:50:45AM +0200, Hannes Reinecke wrote:
> >> That's what I thought, too. Hence the patch.
> >> But if we set the default to 16 byte cdbs you can of course ignore
> >> the patch.
> >
> > I
On Fri, Oct 19 2007 at 20:33 +0200, Matthew Wilcox <[EMAIL PROTECTED]> wrote:
> This fairly naive patch introduces alloc_cmnd and destroy_cmnd. I'm not
> exactly happy about passing down the gfp_mask -- I'd prefer to be able
> to allocate scsi_cmnds before we grab the queue_lock (and hence get
> r
FUJITA Tomonori wrote:
> On Tue, 23 Oct 2007 13:47:20 +0530
> "Thayumanavar Sachithanantham" <[EMAIL PROTECTED]> wrote:
>
>> Hi All,
>>
>> Does the recent target mode support added for tgt support target mode
>> for qla chipset (qla24xx series)?
>
> We've been trying:
>
> http://marc.info/?t=118
FUJITA Tomonori wrote:
On Tue, 23 Oct 2007 13:47:20 +0530
"Thayumanavar Sachithanantham" <[EMAIL PROTECTED]> wrote:
Hi All,
Does the recent target mode support added for tgt support target mode
for qla chipset (qla24xx series)?
We've been trying:
http://marc.info/?t=11885798674&r=1&w=
On Mon, Oct 22 2007, [EMAIL PROTECTED] wrote:
> Jens Axboe [EMAIL PROTECTED] wrote:
> > Current code is below, btw. Not a lot of changes, iirc it's just the
> > delete-always, a missing export, delete timer on empty list.
> >
> > +void blk_add_timer(struct request *req)
> > +{
> > + struct reque
Thayumanavar Sachithanantham wrote:
> Hi All,
>
> Does the recent target mode support added for tgt support target mode
> for qla chipset (qla24xx series)?
I'm in the middle of adding the target mode support for qla24xx and newer
series on top of the recent target mode patch (submitted by Tomonor
On Mon, Oct 22, 2007 at 04:12:06PM +0400, Alexey Dobriyan wrote:
> Steps to reproduce:
>
> modprobe sr_mod
To clarify: this is done during boot sequence.
> rmmod sr_mod
> modprobe sr_mod
This -- by hand.
> BUG: unable to handle kernel paging request at virtual address f881b9f
Hi Fujita,
Thanks for the reply. Just as an information there is target mode
support for the chipsets ISP 2422 and ISP 2432 (4G some of QLA24xxx)
at the SCST trunk(. The associated firmware files are as avaliable
along with it(qla_isp directory of the trunk).
I haven't tested any target mode supp
On Tue, 23 Oct 2007 13:47:20 +0530
"Thayumanavar Sachithanantham" <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Does the recent target mode support added for tgt support target mode
> for qla chipset (qla24xx series)?
We've been trying:
http://marc.info/?t=11885798674&r=1&w=2
But I heard that t
Hi All,
Does the recent target mode support added for tgt support target mode
for qla chipset (qla24xx series)?
Can anyone say what isp chipset qla2462 belong to? ( i don't have 2462
with this and i need this info if possible).
Thanks,
Thayumanavar S.
-
To unsubscribe from this list: send the lin
Jeff Garzik wrote:
> Alan Cox wrote:
>>> 2) Once we identified, over time, the set of drives affected by this
>>> 3112 quirk (aka drives that didn't fully comply to SATA spec), the
>>> debugging of corruption cases largely shifted to the standard
>>> routine: update the BIOS, replace the
>>> cables
30 matches
Mail list logo
