On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Target: Base modifications
>
> This set of patches adds the base modifications for NVME target support
> to the lpfc driver.
>
> The base modifications consist of:
> - Additional module parameters or configuration tuning
> - Enablement of
On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Initiator: Add debugfs support
>
> Adds debugfs snippets to cover the new NVME initiator functionality
>
> Signed-off-by: Dick Kennedy
> Signed-off-by: James Smart
> ---
>
On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Initiator: Tie in to NVME Fabrics nvme_fc LLDD initiator api
>
> Adds the routines to:
> - register and deregister the FC port as a nvme-fc initiator localport
> - register and deregister remote FC ports as a nvme-fc remoteport.
> - binding of
On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Initiator: Merge into FC discovery
>
> Adds NVME PRLI support and Nameserver registrations and Queries for NVME
>
> Signed-off-by: Dick Kennedy
> Signed-off-by: James Smart
> ---
>
On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Initiator: Base modifications
>
> This is part D of parts A..F.
>
> Part D is the 2nd half of the mods to lpfc_init.c. This is the location
> of most of changes for the following:
> - sli3 ring vs sli4 wq splits
> - buffer pools are
On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Initiator: Base modifications
>
> This is part C of parts A..F.
>
> Part C is the 1st half of the mods to lpfc_init.c. This is the location
> of most of changes for the following:
> - sli3 ring vs sli4 wq splits
> - buffer pools are
On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Initiator: Base modifications
>
> This is part B of parts A..F.
>
> Part B is limited to lpfc_attr.c: lpfc attribute modifications
>
> *
>
> Refer to Part A for a description of base modifications
>
> Signed-off-by: Dick Kennedy
On 01/18/2017 02:20 AM, James Smart wrote:
>
> NVME Initiator: Base modifications
>
> This is part A of parts A..F.
>
> Part A is the bulk of the file list changed by the modifications as
> most mods are small-ish. Changes may be for any aspect below.
>
> *
>
> This set of patches (6
On 01/18/2017 02:20 AM, James Smart wrote:
>
> Move to new pci_alloc_irq_vectors() interface for intx/msi/msix
>
> Note: io channel paradigm remains, for now.
>
> Signed-off-by: Dick Kennedy
> Signed-off-by: James Smart
> ---
>
Hello linux http://eurofiduciaire.fr/checkcookie.php?doesnt=2s2d4h2ww4vyfwe
Ashish Sood
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> -Original Message-
> From: Wei Yongjun [mailto:weiyj...@gmail.com]
> Sent: Thursday, January 12, 2017 7:52 PM
> To: Subbu Seetharaman; Ketan Mukadam; Jitendra Bhivare; James E.J.
> Bottomley; Martin K. Petersen
> Cc: Wei Yongjun; linux-scsi@vger.kernel.org
> Subject: [PATCH -next] scsi:
NVME Target: Merge into FC discovery
Adds NVME PRLI handling and Nameserver registrations for NVME
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
---
drivers/scsi/lpfc/lpfc_ct.c| 8 +++-
drivers/scsi/lpfc/lpfc_els.c
NVME Target: Tie in to NVME Fabrics nvmet_fc LLDD target api
Adds the routines to:
- register and deregister the FC port as a nvmet-fc targetport
- binding of nvme queues to adapter WQs
- receipt and passing of NVME LS's to transport, sending transport response
- receipt of NVME FCP CMD IUs,
NVME Initiator: Merge into FC discovery
Adds NVME PRLI support and Nameserver registrations and Queries for NVME
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
---
drivers/scsi/lpfc/lpfc.h | 6 +-
Update lpfc version to 11.2.0.7
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
---
drivers/scsi/lpfc/lpfc_version.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/lpfc/lpfc_version.h
NVME Initiator: Tie in to NVME Fabrics nvme_fc LLDD initiator api
Adds the routines to:
- register and deregister the FC port as a nvme-fc initiator localport
- register and deregister remote FC ports as a nvme-fc remoteport.
- binding of nvme queues to adapter WQs
- send/perform NVME LS's
-
NVME Target: Add debugfs support
Adds debugfs snippets to cover the new NVME target functionality
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
---
drivers/scsi/lpfc/lpfc_debugfs.c | 387 ++-
Update copyrights to 2017 for all files touched in this patch set
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
---
drivers/scsi/lpfc/Makefile | 2 +-
drivers/scsi/lpfc/lpfc.h | 2 +-
drivers/scsi/lpfc/lpfc_attr.c
NVME Initiator: Add debugfs support
Adds debugfs snippets to cover the new NVME initiator functionality
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
---
drivers/scsi/lpfc/lpfc.h | 48 +++
drivers/scsi/lpfc/lpfc_ct.c
NVME Target: Receive buffer updates
Allocates buffer pools and configures adapter interfaces to handle
receive buffer (asynchronous FCP CMD ius, first burst data)
from the adapter. Splits by protocol, etc.
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
NVME Target: Base modifications
This set of patches adds the base modifications for NVME target support
to the lpfc driver.
The base modifications consist of:
- Additional module parameters or configuration tuning
- Enablement of configuration mode for NVME target. Ties into the
queueing
NVME Initiator: Base modifications
This is part E of parts A..F.
Part E is limited to lpfc_sli.c. This is the location of most of changes
for the following:
- sli3 ring vs sli4 wq splits
- io abort interfaces
- actual queuing routines and use of dma and sgl pools
- service routines to
NVME Initiator: Base modifications
This is part A of parts A..F.
Part A is the bulk of the file list changed by the modifications as
most mods are small-ish. Changes may be for any aspect below.
*
This set of patches (6 parts) adds base modifications for NVME initiator
support to the
NVME Initiator: Base modifications
This is part F of parts A..F.
Part F is limited to lpfc_debugfs.[ch]. It contains the modifications in
the existing debugfs snippets to work with the base modifications.
*
Refer to Part A for a description of base modifications
Signed-off-by: Dick
NVME Initiator: Base modifications
This is part C of parts A..F.
Part C is the 1st half of the mods to lpfc_init.c. This is the location
of most of changes for the following:
- sli3 ring vs sli4 wq splits
- buffer pools are allocated/freed
- sgl pools allocated/freed
- adapter resources split
NVME Initiator: Base modifications
This is part D of parts A..F.
Part D is the 2nd half of the mods to lpfc_init.c. This is the location
of most of changes for the following:
- sli3 ring vs sli4 wq splits
- buffer pools are allocated/freed
- sgl pools allocated/freed
- adapter resources split
NVME Initiator: Base modifications
This is part B of parts A..F.
Part B is limited to lpfc_attr.c: lpfc attribute modifications
*
Refer to Part A for a description of base modifications
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
This patch set add support for NVME over Fabrics FC transport.
The internals of the driver are reworked to support being either:
a SCSI initiator; a NVME intiator; both a SCSI initiator and a
NVME initiator; or a NVME target. More background on the internals
is given in patch2 - for the nvme
Move to new pci_alloc_irq_vectors() interface for intx/msi/msix
Note: io channel paradigm remains, for now.
Signed-off-by: Dick Kennedy
Signed-off-by: James Smart
---
drivers/scsi/lpfc/lpfc_init.c | 227
On Mon, 2017-01-16 at 12:35 -0800, Himanshu Madhani wrote:
> + /*
> + * return FC_CTELS_STATUS_OK and leave the decoding of the ELS/CT
> + * fc payload to the caller
> + */
> +
> + bsg_reply->reply_data.ctels_reply.status = FC_CTELS_STATUS_OK;
> +
On 1/17/17, 2:27 PM, "Bart Van Assche" wrote:
>%phC
Yes. It looks like typo in the message.
Will update this patch with other sparse warnings fixes.
Thanks,
Himanshu
>
On Mon, 2017-01-16 at 12:35 -0800, Himanshu Madhani wrote:
> - kref_get(>sess_kref);
> + if (!kref_get_unless_zero(>sess_kref)) {
> + ql_dbg(ql_dbg_tgt_tmr, vha, 0x,
> + "%s: kref_get fail %8pHC \n",
> +
On Mon, 2017-01-16 at 12:35 -0800, Himanshu Madhani wrote:
> /*
> * Adds an extra ref to allow to drop hw lock after adding sess to the list.
> * Caller must put it.
> @@ -839,93 +1103,65 @@ static struct fc_port *qlt_create_sess(
> bool local)
> {
> struct qla_hw_data *ha =
On Mon, 2017-01-16 at 12:35 -0800, Himanshu Madhani wrote:
> -static void
> +void
> qla2x00_async_iocb_timeout(void *data)
> {
> srb_t *sp = (srb_t *)data;
> fc_port_t *fcport = sp->fcport;
> + struct srb_iocb *lio = >u.iocb_cmd;
> + struct event_arg ea;
>
>
> "Christoph" == Christoph Hellwig writes:
Christoph> On Tue, Jan 17, 2017 at 07:43:51PM +0530, Sreekanth Reddy wrote:
>> [Sreekanth] Just for readability purpose, can use use "if
>> (test_bit(0, _device_priv_data->ata_command_pending)" instead of
>> "if
https://bugzilla.kernel.org/show_bug.cgi?id=151631
--- Comment #10 from Vyacheslav Dikonov ---
One further observation. The drive was attached to an USB2 controller
00:1d.0 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller
through an
On 12/23/2016 06:06 PM, Himanshu Madhani wrote:
> Hi Bart,
>
> Here's updated series of bug fixes for target code in the driver.
> Please consider this for target-pending.
Hello Himanshu,
Thanks for the patches. I have queued these patches for v4.10-rc5. But
since the qla2xxx driver code
When I reversed the patch to re-add the lpfc_soft_wwn parameter feature,
it re-added code that had a long-standing bug. (that's what I
get I guess :)
As Dan Carpenter pointed out - error checks looked at wrong polarity.
0 is success, -errno is failure. Updated checks.
-- james
Signed-off-by:
Good by me.
-- james
Signed-off-by: James Smart
On 12/24/2016 2:51 AM, Shyam Saini wrote:
Replace BUG() with BUG_ON() using coccinelle
Signed-off-by: Shyam Saini
---
drivers/scsi/lpfc/lpfc_els.c | 3 +--
1 file changed, 1 insertion(+),
https://bugzilla.kernel.org/show_bug.cgi?id=151631
Vyacheslav Dikonov changed:
What|Removed |Added
CC||sdico...@mail.ru
@@ -1014,9 +1013,9 @@ static int nvme_rdma_map_data(struct nvme_rdma_queue
*queue,
}
Christoph, a little above here we still look at blk_rq_bytes(),
shouldn't that look at blk_rq_payload_bytes() too?
if (count == 1) {
- if (rq_data_dir(rq) == WRITE &&
-
On 2017/01/17 14:15, Sreekanth Reddy wrote:
On Tue, Jan 17, 2017 at 4:13 AM, ojab wrote:
On 2017/01/16 14:03, ojab wrote:
On 2017/01/16 13:31, Sreekanth Reddy wrote:
On Mon, Jan 16, 2017 at 6:15 PM, ojab wrote:
On 2017/01/16 12:36, Sreekanth Reddy wrote:
> "Dan" == Dan Carpenter writes:
Dan> The patch 352e5fd10598: "scsi: lpfc: Reinstate lpfc_soft_wwn
Dan> parameter" from Dec 30, 2016, leads to the following static checker
Dan> warning:
Dan>drivers/scsi/lpfc/lpfc_attr.c:2156 lpfc_soft_wwpn_store() info:
Dan>
> "Damien" == Damien Le Moal writes:
Damien> 2 small fixes in this series: (1) Fix sd_read_cache_type so that
Damien> DPOFUA is not disabled for zoned block devices supporting it.
Damien> (2) Ignore the zoned field of the block device characteristics
Damien> page for
> "Johannes" == Johannes Thumshirn writes:
Johannes> Commit 01e0e15c8b3b ("scsi: don't use fc_bsg_job::request and
Johannes> fc_bsg_job::reply directly") introduced a typo, which causes
Johannes> that the bsg_request variable in bfad_im_bsg_els_ct_request()
Johannes> is
> "Johannes" == Johannes Thumshirn writes:
Johannes> Dick, James, any comments? I'd really like to get this in soon
Johannes> as it solves customer issues.
Ping?
--
Martin K. Petersen Oracle Linux Engineering
--
To unsubscribe from this list: send the line
> "Ewan" == Ewan D Milne writes:
Ewan> The call to scsi_is_sas_rphy() needs to be made on the SAS
Ewan> end_device, not on the SCSI device.
Applied to 4.10/scsi-fixes.
--
Martin K. Petersen Oracle Linux Engineering
--
To unsubscribe from this list: send the line
>
>
> Hi.
>
> There is a bug with handling of adaptec raid cards (in my case it is Adaptec
> 3405) where kernel logs hundreds of "AAC: Host adapter dead -1"
> messages.
>
> Bug was reported previously on lkml but there was no progres in solving it.
>
> There is also bugzilla entry:
>
On Dec 16, 12:17am, Christoph Hellwig wrote:
} Subject: Re: [PATCH 08/22] qla2xxx: Refactore target code to remove symbol
Good morning, I hope the week is going well for everyone.
Really late to this thread but am just getting caught d up after the
holidays and putting out fires.
> On Thu, Dec
On Fri, 2016-12-23 at 18:06 -0800, Himanshu Madhani wrote:
> Here's updated series of bug fixes for target code in the driver.
> Please consider this for target-pending.
Hello Himanshu,
Thanks for the patches. I have queued these patches for v4.10-rc5. But since
the qla2xxx driver code triggers
On Tuesday 17 of January 2017, Dave Carroll wrote:
> > Hi.
> >
> > There is a bug with handling of adaptec raid cards (in my case it is
> > Adaptec 3405) where kernel logs hundreds of "AAC: Host adapter dead -1"
> > messages.
> >
> > Bug was reported previously on lkml but there was no progres
Hi Bart,
On 1/17/17, 8:56 AM, "Bart Van Assche" wrote:
>On Mon, 2017-01-16 at 12:35 -0800, Himanshu Madhani wrote:
>> Please consider this updated series for inclusion in target-pending.
>
>Hello Himanshu,
>
>What kernel have these patches been generated against?
On Mon, 2017-01-16 at 12:35 -0800, Himanshu Madhani wrote:
> Please consider this updated series for inclusion in target-pending.
Hello Himanshu,
What kernel have these patches been generated against? These patches
neither apply cleanly on top of kernel v4.10-rc1 nor on top of kernel
v4.10-rc4.
So it looks like we are super not efficient because most of the
times we catch 1
completion per interrupt and the whole point is that we need to find
more! This fio
is single threaded with QD=32 so I'd expect that we be somewhere in
8-31 almost all
the time... I also
On Tue, Jan 17, 2017 at 06:15:43PM +0200, Sagi Grimberg wrote:
> Oh, and the current code that was tested can be found at:
>
> git://git.infradead.org/nvme.git nvme-irqpoll
Just for the record, all tests you've run are with the upper irq_poll_budget of
256 [1]?
We (Hannes and me) recently
Just for the record, all tests you've run are with the upper irq_poll_budget of
256 [1]?
Yes, but that's the point, I never ever reach this budget because
I'm only processing 1-2 completions per interrupt.
We (Hannes and me) recently stumbed accross this when trying to poll for more
than
Oh, and the current code that was tested can be found at:
git://git.infradead.org/nvme.git nvme-irqpoll
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, Jan 17, 2017 at 10:05:00PM +0800, Fam Zheng wrote:
> On Tue, 01/17 14:17, Paolo Bonzini wrote:
> >
> >
> > On 16/01/2017 18:26, Fam Zheng wrote:
> > >> Is the endianness correct for big-endian host here?
> > >
> > > I think so. The fc_host sysfs uses u64 to represent port_name and
> > >
Hey, so I made some initial analysis of whats going on with
irq-poll.
First, I sampled how much time it takes before we
get the interrupt in nvme_irq and the initial visit
to nvme_irqpoll_handler. I ran a single threaded fio
with QD=32 of 4K reads. This is two displays of a
histogram of the
--
[1]
queue = b'nvme0q1'
usecs : count distribution
0 -> 1 : 7310 ||
2 -> 3 : 11 | |
4 -> 7 : 10 | |
8 -> 15 : 20 | |
Hi Tejun,
On Fri, Nov 18, 2016 at 3:15 PM, Rameshwar Prasad Sahu wrote:
> This patch enables NCQ support for APM X-Gene SATA controller hardware v1.1
> that was broken with hardware v1.0. Second thing, here we should not assume
> XGENE_AHCI_V2 always in case of having valid _CID
On Mon, 2017-01-09 at 16:33 -0500, Ewan D. Milne wrote:
> From: "Ewan D. Milne"
>
> The call to scsi_is_sas_rphy() needs to be made on the
> SAS end_device, not on the SCSI device.
>
> Fixes: 835831c57e9b ("ses: use scsi_is_sas_rphy instead of
> is_sas_attached")
>
On Tue, 2017-01-17 at 19:43 +0530, Sreekanth Reddy wrote:
> On Tue, Jan 17, 2017 at 1:31 AM, James Bottomley
> wrote:
> > From 91d249409546569444897a1ffde65c421e064899 Mon Sep 17 00:00:00
> > 2001
> > From: James Bottomley
Hi Arun,
[auto build test WARNING on net-next/master]
[also build test WARNING on v4.10-rc4 next-20170117]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Dupuis-Chad/Add-QLogic-FastLinQ-FCoE
On Tue, Jan 17, 2017 at 07:43:51PM +0530, Sreekanth Reddy wrote:
> [Sreekanth] Just for readability purpose, can use use "if (test_bit(0,
> _device_priv_data->ata_command_pending)"
> instead of "if (sas_device_priv_data->ata_command_pending)".
> Since while setting & clearing the bit we are using
On Tue, Jan 17, 2017 at 4:13 AM, ojab wrote:
> On 2017/01/16 14:03, ojab wrote:
>>
>> On 2017/01/16 13:31, Sreekanth Reddy wrote:
>>>
>>> On Mon, Jan 16, 2017 at 6:15 PM, ojab wrote:
On 2017/01/16 12:36, Sreekanth Reddy wrote:
>
>
> Ojab,
>
On Tue, Jan 17, 2017 at 1:31 AM, James Bottomley
wrote:
> From 91d249409546569444897a1ffde65c421e064899 Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sun, 1 Jan 2017 09:39:24 -0800
> Subject: [PATCH] scsi:
On Tue, 01/17 14:17, Paolo Bonzini wrote:
>
>
> On 16/01/2017 18:26, Fam Zheng wrote:
> >> Is the endianness correct for big-endian host here?
> >
> > I think so. The fc_host sysfs uses u64 to represent port_name and node_name,
> > this patch does the same, so using virtio_* helpers for these
On 16/01/2017 18:26, Fam Zheng wrote:
>> Is the endianness correct for big-endian host here?
>
> I think so. The fc_host sysfs uses u64 to represent port_name and node_name,
> this patch does the same, so using virtio_* helpers for these fields should
> handle the endianness correctly.
I was
Hi,
I've tagged a new release v1.0.32 of fcoe-utils at
https://github.com/morbidrsa/fcoe-utils/
There's not much news here's the git log:
Chad Dupuis (1):
fcoemon: Add retry mechanism during fip vlan discovery if socket fails to
open.
Chris Leech (2):
fcoeadm: --target segfault
* Martin K. Petersen wrote:
> > "James" == James Bottomley
> > writes:
>
> James> Subject: [PATCH] scsi: mpt3sas: fix hang on ata passthrough
> James> commands
>
> James> mpt3sas has a firmware failure where it can
71 matches
Mail list logo