All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Duncan <lduncan@suse.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, open-iscsi@googlegroups.com
Subject: Re: [PATCH] Use ida_simple for SCSI iSCSI transport session id
Date: Mon, 7 Mar 2016 17:02:32 -0800	[thread overview]
Message-ID: <56DE24A8.2060305@suse.com> (raw)
In-Reply-To: <1455299691.2396.45.camel@HansenPartnership.com>

On 02/12/2016 09:54 AM, James Bottomley wrote:
> On Fri, 2016-02-12 at 09:38 -0800, Lee Duncan wrote:
>> The scsi_transport_iscsi module already uses the ida_simple
>> routines for managing the target ID, if requested to do
>> so. This change replaces an ever-increasing atomic integer
>> that tracks the session ID itself with the ida_simple
>> family of routines. This means that the session ID
>> will be reclaimed and can be reused when the session
>> is freed.
> 
> Is reusing session ID's really a good idea?  For sequential sessions it
> means that the ID of the next session will be re-used, i.e. the same as
> the previous sessions, which could lead to target confusion.  I think
> local uniqueness of session IDs is more important than wrap around
> because sessions are short lived entities and the chances of the same
> session being alive by the time we've wrapped is pretty tiny.
> 
> If you can demostrate a multi-target problem, perhaps we should rather
> fix this by making the next session id a target local quantity?
> 
> James
> 

It looks like Mike and Chris are good with it. And I'd really like to
get rid of yet another atomic int.

Are you satisfied with this one?
-- 
Lee

  parent reply	other threads:[~2016-03-08  1:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 17:38 [PATCH] Use ida_simple for SCSI iSCSI transport session id Lee Duncan
2016-02-12 17:38 ` Lee Duncan
     [not found] ` <1455298733-18651-1-git-send-email-lduncan-IBi9RG/b67k@public.gmane.org>
2016-02-12 17:54   ` James Bottomley
2016-02-12 17:54     ` James Bottomley
     [not found]     ` <1455299691.2396.45.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2016-02-12 22:13       ` Mike Christie
2016-02-12 22:13         ` Mike Christie
2016-02-15 18:26     ` Chris Leech
     [not found]       ` <20160215182653.pvo6crry2wqwgjso-r8IHplWLGbA5tHQWs+pTeqPFFGjUI2lm2LY78lusg7I@public.gmane.org>
2016-02-16 18:40         ` Mike Christie
2016-02-16 18:40           ` Mike Christie
     [not found]           ` <56C36D0C.3030002-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2016-02-17 22:37             ` Chris Leech
2016-02-17 22:37               ` Chris Leech
2016-03-08  1:02     ` Lee Duncan [this message]
     [not found]       ` <56DE24A8.2060305-IBi9RG/b67k@public.gmane.org>
2016-03-08  2:15         ` Martin K. Petersen
2016-03-08  2:15           ` Martin K. Petersen
2016-03-08 17:21   ` Chris Leech
2016-03-08 17:21     ` Chris Leech
2016-03-09  8:43   ` Johannes Thumshirn
2016-03-09  8:43     ` Johannes Thumshirn

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=56DE24A8.2060305@suse.com \
    --to=lduncan@suse.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=open-iscsi@googlegroups.com \
    /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.