Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1352518
| From | Lee Duncan <lduncan@suse.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] Use ida_simple for SCSI iSCSI transport session id |
| Date | 2016-03-08 02:10 +0100 |
| Message-ID | <raejT-2dp-1@gated-at.bofh.it> (permalink) |
| References | <r1q0W-1Ii-31@gated-at.bofh.it> <r1qaB-1Lx-1@gated-at.bofh.it> |
| Organization | SUSE |
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
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH] Use ida_simple for SCSI iSCSI transport session id Lee Duncan <lduncan@suse.com> - 2016-03-08 02:10 +0100 Re: [PATCH] Use ida_simple for SCSI iSCSI transport session id "Martin K. Petersen" <martin.petersen@oracle.com> - 2016-03-08 03:20 +0100
csiph-web