All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saeed Bishara <Saeed.Bishara@il.marvell.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: can_queue modification within select_queue_depths
Date: Thu, 19 Aug 2004 14:58:38 +0300	[thread overview]
Message-ID: <412495EE.1000904@il.marvell.com> (raw)
In-Reply-To: <20040819121902.A8273@infradead.org>

yes I'm working on Marvells sata devices, I'm still waiting for Jeff for 
an initial libata version.


Christoph Hellwig wrote:

>On Wed, Aug 18, 2004 at 02:17:05PM +0300, Saeed Bishara wrote:
>  
>
>>Hi,
>>    is it allowed to modify the host can_queue with select_queue_depths 
>>function?
>>    
>>
>
>Yes.
>
>  
>
>>    if yes, is it needed to lock/unlock io_request_lock ?
>>thanks  
>>    
>>
>
>Dunno about 2.4 locking, but given this is at init time and thus implicitly
>serialized I wouldn't care too much about locking.
>
>
>BTW, if you happen to work on a driver for the marvell SATA part please
>talk to Jeff Garzik who is doing a libata driver for it.  Also note that
>we're not going to accept pure SCSI LLDDs for (S)ATA hardware.
>
>  
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>  
>



      reply	other threads:[~2004-08-19 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 11:17 can_queue modification within select_queue_depths Saeed Bishara
2004-08-19 11:19 ` Christoph Hellwig
2004-08-19 11:58   ` Saeed Bishara [this message]

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=412495EE.1000904@il.marvell.com \
    --to=saeed.bishara@il.marvell.com \
    --cc=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.