2007-02-13 08:16:18 +08:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2006 Chelsio, Inc. All rights reserved.
|
|
|
|
*
|
|
|
|
* This software is available to you under a choice of one of two
|
|
|
|
* licenses. You may choose to be licensed under the terms of the GNU
|
|
|
|
* General Public License (GPL) Version 2, available from the file
|
|
|
|
* COPYING in the main directory of this source tree, or the
|
|
|
|
* OpenIB.org BSD license below:
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or
|
|
|
|
* without modification, are permitted provided that the following
|
|
|
|
* conditions are met:
|
|
|
|
*
|
|
|
|
* - Redistributions of source code must retain the above
|
|
|
|
* copyright notice, this list of conditions and the following
|
|
|
|
* disclaimer.
|
|
|
|
*
|
|
|
|
* - Redistributions in binary form must reproduce the above
|
|
|
|
* copyright notice, this list of conditions and the following
|
|
|
|
* disclaimer in the documentation and/or other materials
|
|
|
|
* provided with the distribution.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
|
|
|
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
|
|
|
* MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
|
|
|
* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
|
|
|
|
* BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
|
|
|
|
* ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
|
|
|
|
* CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
|
|
* SOFTWARE.
|
|
|
|
*/
|
|
|
|
/* Crude resource management */
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/random.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/kfifo.h>
|
|
|
|
#include <linux/spinlock.h>
|
|
|
|
#include <linux/errno.h>
|
|
|
|
#include "cxio_resource.h"
|
|
|
|
#include "cxio_hal.h"
|
|
|
|
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
static struct kfifo rhdl_fifo;
|
2007-02-13 08:16:18 +08:00
|
|
|
static spinlock_t rhdl_fifo_lock;
|
|
|
|
|
|
|
|
#define RANDOM_SIZE 16
|
|
|
|
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
static int __cxio_init_resource_fifo(struct kfifo *fifo,
|
2007-02-13 08:16:18 +08:00
|
|
|
spinlock_t *fifo_lock,
|
|
|
|
u32 nr, u32 skip_low,
|
|
|
|
u32 skip_high,
|
|
|
|
int random)
|
|
|
|
{
|
|
|
|
u32 i, j, entry = 0, idx;
|
|
|
|
u32 random_bytes;
|
|
|
|
u32 rarray[16];
|
|
|
|
spin_lock_init(fifo_lock);
|
|
|
|
|
2009-12-22 06:37:27 +08:00
|
|
|
if (kfifo_alloc(fifo, nr * sizeof(u32), GFP_KERNEL))
|
2007-02-13 08:16:18 +08:00
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
for (i = 0; i < skip_low + skip_high; i++)
|
2009-12-22 06:37:28 +08:00
|
|
|
kfifo_in(fifo, (unsigned char *) &entry, sizeof(u32));
|
2007-02-13 08:16:18 +08:00
|
|
|
if (random) {
|
|
|
|
j = 0;
|
2013-05-08 07:18:16 +08:00
|
|
|
random_bytes = prandom_u32();
|
2007-02-13 08:16:18 +08:00
|
|
|
for (i = 0; i < RANDOM_SIZE; i++)
|
|
|
|
rarray[i] = i + skip_low;
|
|
|
|
for (i = skip_low + RANDOM_SIZE; i < nr - skip_high; i++) {
|
|
|
|
if (j >= RANDOM_SIZE) {
|
|
|
|
j = 0;
|
2013-05-08 07:18:16 +08:00
|
|
|
random_bytes = prandom_u32();
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
idx = (random_bytes >> (j * 2)) & 0xF;
|
2009-12-22 06:37:28 +08:00
|
|
|
kfifo_in(fifo,
|
2007-02-13 08:16:18 +08:00
|
|
|
(unsigned char *) &rarray[idx],
|
|
|
|
sizeof(u32));
|
|
|
|
rarray[idx] = i;
|
|
|
|
j++;
|
|
|
|
}
|
|
|
|
for (i = 0; i < RANDOM_SIZE; i++)
|
2009-12-22 06:37:28 +08:00
|
|
|
kfifo_in(fifo,
|
2007-02-13 08:16:18 +08:00
|
|
|
(unsigned char *) &rarray[i],
|
|
|
|
sizeof(u32));
|
|
|
|
} else
|
|
|
|
for (i = skip_low; i < nr - skip_high; i++)
|
2009-12-22 06:37:28 +08:00
|
|
|
kfifo_in(fifo, (unsigned char *) &i, sizeof(u32));
|
2007-02-13 08:16:18 +08:00
|
|
|
|
|
|
|
for (i = 0; i < skip_low + skip_high; i++)
|
2009-12-22 06:37:29 +08:00
|
|
|
if (kfifo_out_locked(fifo, (unsigned char *) &entry,
|
|
|
|
sizeof(u32), fifo_lock) != sizeof(u32))
|
|
|
|
break;
|
2007-02-13 08:16:18 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
static int cxio_init_resource_fifo(struct kfifo *fifo, spinlock_t * fifo_lock,
|
2007-02-13 08:16:18 +08:00
|
|
|
u32 nr, u32 skip_low, u32 skip_high)
|
|
|
|
{
|
|
|
|
return (__cxio_init_resource_fifo(fifo, fifo_lock, nr, skip_low,
|
|
|
|
skip_high, 0));
|
|
|
|
}
|
|
|
|
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
static int cxio_init_resource_fifo_random(struct kfifo *fifo,
|
2007-02-13 08:16:18 +08:00
|
|
|
spinlock_t * fifo_lock,
|
|
|
|
u32 nr, u32 skip_low, u32 skip_high)
|
|
|
|
{
|
|
|
|
|
|
|
|
return (__cxio_init_resource_fifo(fifo, fifo_lock, nr, skip_low,
|
|
|
|
skip_high, 1));
|
|
|
|
}
|
|
|
|
|
|
|
|
static int cxio_init_qpid_fifo(struct cxio_rdev *rdev_p)
|
|
|
|
{
|
|
|
|
u32 i;
|
|
|
|
|
|
|
|
spin_lock_init(&rdev_p->rscp->qpid_fifo_lock);
|
|
|
|
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
if (kfifo_alloc(&rdev_p->rscp->qpid_fifo, T3_MAX_NUM_QP * sizeof(u32),
|
2009-12-22 06:37:27 +08:00
|
|
|
GFP_KERNEL))
|
2007-02-13 08:16:18 +08:00
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
for (i = 16; i < T3_MAX_NUM_QP; i++)
|
|
|
|
if (!(i & rdev_p->qpmask))
|
2009-12-22 06:37:28 +08:00
|
|
|
kfifo_in(&rdev_p->rscp->qpid_fifo,
|
2007-02-13 08:16:18 +08:00
|
|
|
(unsigned char *) &i, sizeof(u32));
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int cxio_hal_init_rhdl_resource(u32 nr_rhdl)
|
|
|
|
{
|
|
|
|
return cxio_init_resource_fifo(&rhdl_fifo, &rhdl_fifo_lock, nr_rhdl, 1,
|
|
|
|
0);
|
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_destroy_rhdl_resource(void)
|
|
|
|
{
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
kfifo_free(&rhdl_fifo);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/* nr_* must be power of 2 */
|
|
|
|
int cxio_hal_init_resource(struct cxio_rdev *rdev_p,
|
|
|
|
u32 nr_tpt, u32 nr_pbl,
|
|
|
|
u32 nr_rqt, u32 nr_qpid, u32 nr_cqid, u32 nr_pdid)
|
|
|
|
{
|
|
|
|
int err = 0;
|
|
|
|
struct cxio_hal_resource *rscp;
|
|
|
|
|
|
|
|
rscp = kmalloc(sizeof(*rscp), GFP_KERNEL);
|
|
|
|
if (!rscp)
|
|
|
|
return -ENOMEM;
|
|
|
|
rdev_p->rscp = rscp;
|
|
|
|
err = cxio_init_resource_fifo_random(&rscp->tpt_fifo,
|
|
|
|
&rscp->tpt_fifo_lock,
|
|
|
|
nr_tpt, 1, 0);
|
|
|
|
if (err)
|
|
|
|
goto tpt_err;
|
|
|
|
err = cxio_init_qpid_fifo(rdev_p);
|
|
|
|
if (err)
|
|
|
|
goto qpid_err;
|
|
|
|
err = cxio_init_resource_fifo(&rscp->cqid_fifo, &rscp->cqid_fifo_lock,
|
|
|
|
nr_cqid, 1, 0);
|
|
|
|
if (err)
|
|
|
|
goto cqid_err;
|
|
|
|
err = cxio_init_resource_fifo(&rscp->pdid_fifo, &rscp->pdid_fifo_lock,
|
|
|
|
nr_pdid, 1, 0);
|
|
|
|
if (err)
|
|
|
|
goto pdid_err;
|
|
|
|
return 0;
|
|
|
|
pdid_err:
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
kfifo_free(&rscp->cqid_fifo);
|
2007-02-13 08:16:18 +08:00
|
|
|
cqid_err:
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
kfifo_free(&rscp->qpid_fifo);
|
2007-02-13 08:16:18 +08:00
|
|
|
qpid_err:
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
kfifo_free(&rscp->tpt_fifo);
|
2007-02-13 08:16:18 +08:00
|
|
|
tpt_err:
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* returns 0 if no resource available
|
|
|
|
*/
|
2009-12-22 06:37:27 +08:00
|
|
|
static u32 cxio_hal_get_resource(struct kfifo *fifo, spinlock_t * lock)
|
2007-02-13 08:16:18 +08:00
|
|
|
{
|
|
|
|
u32 entry;
|
2009-12-22 06:37:28 +08:00
|
|
|
if (kfifo_out_locked(fifo, (unsigned char *) &entry, sizeof(u32), lock))
|
2007-02-13 08:16:18 +08:00
|
|
|
return entry;
|
|
|
|
else
|
|
|
|
return 0; /* fifo emptry */
|
|
|
|
}
|
|
|
|
|
2009-12-22 06:37:27 +08:00
|
|
|
static void cxio_hal_put_resource(struct kfifo *fifo, spinlock_t * lock,
|
|
|
|
u32 entry)
|
2007-02-13 08:16:18 +08:00
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
BUG_ON(
|
2009-12-22 06:37:28 +08:00
|
|
|
kfifo_in_locked(fifo, (unsigned char *) &entry, sizeof(u32), lock)
|
2009-12-22 06:37:27 +08:00
|
|
|
== 0);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
u32 cxio_hal_get_stag(struct cxio_hal_resource *rscp)
|
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
return cxio_hal_get_resource(&rscp->tpt_fifo, &rscp->tpt_fifo_lock);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_put_stag(struct cxio_hal_resource *rscp, u32 stag)
|
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
cxio_hal_put_resource(&rscp->tpt_fifo, &rscp->tpt_fifo_lock, stag);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
u32 cxio_hal_get_qpid(struct cxio_hal_resource *rscp)
|
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
u32 qpid = cxio_hal_get_resource(&rscp->qpid_fifo,
|
|
|
|
&rscp->qpid_fifo_lock);
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s qpid 0x%x\n", __func__, qpid);
|
2007-02-13 08:16:18 +08:00
|
|
|
return qpid;
|
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_put_qpid(struct cxio_hal_resource *rscp, u32 qpid)
|
|
|
|
{
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s qpid 0x%x\n", __func__, qpid);
|
2009-12-22 06:37:27 +08:00
|
|
|
cxio_hal_put_resource(&rscp->qpid_fifo, &rscp->qpid_fifo_lock, qpid);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
u32 cxio_hal_get_cqid(struct cxio_hal_resource *rscp)
|
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
return cxio_hal_get_resource(&rscp->cqid_fifo, &rscp->cqid_fifo_lock);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_put_cqid(struct cxio_hal_resource *rscp, u32 cqid)
|
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
cxio_hal_put_resource(&rscp->cqid_fifo, &rscp->cqid_fifo_lock, cqid);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
u32 cxio_hal_get_pdid(struct cxio_hal_resource *rscp)
|
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
return cxio_hal_get_resource(&rscp->pdid_fifo, &rscp->pdid_fifo_lock);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_put_pdid(struct cxio_hal_resource *rscp, u32 pdid)
|
|
|
|
{
|
2009-12-22 06:37:27 +08:00
|
|
|
cxio_hal_put_resource(&rscp->pdid_fifo, &rscp->pdid_fifo_lock, pdid);
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_destroy_resource(struct cxio_hal_resource *rscp)
|
|
|
|
{
|
kfifo: move struct kfifo in place
This is a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to
many constrains. Only 17 files in the current 2.6.31-rc5 used it.
FIFO's are like list's a very basic thing and a kfifo API which handles
the most use case would save a lot of development time and memory
resources.
I think this are the reasons why kfifo is not in use:
- The API is to simple, important functions are missing
- A fifo can be only allocated dynamically
- There is a requirement of a spinlock whether you need it or not
- There is no support for data records inside a fifo
So I decided to extend the kfifo in a more generic way without blowing up
the API to much. The new API has the following benefits:
- Generic usage: For kernel internal use and/or device driver.
- Provide an API for the most use case.
- Slim API: The whole API provides 25 functions.
- Linux style habit.
- DECLARE_KFIFO, DEFINE_KFIFO and INIT_KFIFO Macros
- Direct copy_to_user from the fifo and copy_from_user into the fifo.
- The kfifo itself is an in place member of the using data structure, this save an
indirection access and does not waste the kernel allocator.
- Lockless access: if only one reader and one writer is active on the fifo,
which is the common use case, no additional locking is necessary.
- Remove spinlock - give the user the freedom of choice what kind of locking to use if
one is required.
- Ability to handle records. Three type of records are supported:
- Variable length records between 0-255 bytes, with a record size
field of 1 bytes.
- Variable length records between 0-65535 bytes, with a record size
field of 2 bytes.
- Fixed size records, which no record size field.
- Preserve memory resource.
- Performance!
- Easy to use!
This patch:
Since most users want to have the kfifo as part of another object,
reorganize the code to allow including struct kfifo in another data
structure. This requires changing the kfifo_alloc and kfifo_init
prototypes so that we pass an existing kfifo pointer into them. This
patch changes the implementation and all existing users.
[akpm@linux-foundation.org: fix warning]
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-12-22 06:37:26 +08:00
|
|
|
kfifo_free(&rscp->tpt_fifo);
|
|
|
|
kfifo_free(&rscp->cqid_fifo);
|
|
|
|
kfifo_free(&rscp->qpid_fifo);
|
|
|
|
kfifo_free(&rscp->pdid_fifo);
|
2007-02-13 08:16:18 +08:00
|
|
|
kfree(rscp);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* PBL Memory Manager. Uses Linux generic allocator.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define MIN_PBL_SHIFT 8 /* 256B == min PBL size (32 entries) */
|
|
|
|
|
|
|
|
u32 cxio_hal_pblpool_alloc(struct cxio_rdev *rdev_p, int size)
|
|
|
|
{
|
|
|
|
unsigned long addr = gen_pool_alloc(rdev_p->pbl_pool, size);
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s addr 0x%x size %d\n", __func__, (u32)addr, size);
|
2007-02-13 08:16:18 +08:00
|
|
|
return (u32)addr;
|
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_pblpool_free(struct cxio_rdev *rdev_p, u32 addr, int size)
|
|
|
|
{
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s addr 0x%x size %d\n", __func__, addr, size);
|
2007-02-13 08:16:18 +08:00
|
|
|
gen_pool_free(rdev_p->pbl_pool, (unsigned long)addr, size);
|
|
|
|
}
|
|
|
|
|
|
|
|
int cxio_hal_pblpool_create(struct cxio_rdev *rdev_p)
|
|
|
|
{
|
2008-05-07 06:03:38 +08:00
|
|
|
unsigned pbl_start, pbl_chunk;
|
|
|
|
|
2007-02-13 08:16:18 +08:00
|
|
|
rdev_p->pbl_pool = gen_pool_create(MIN_PBL_SHIFT, -1);
|
2008-05-07 06:03:38 +08:00
|
|
|
if (!rdev_p->pbl_pool)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
pbl_start = rdev_p->rnic_info.pbl_base;
|
|
|
|
pbl_chunk = rdev_p->rnic_info.pbl_top - pbl_start + 1;
|
|
|
|
|
|
|
|
while (pbl_start < rdev_p->rnic_info.pbl_top) {
|
|
|
|
pbl_chunk = min(rdev_p->rnic_info.pbl_top - pbl_start + 1,
|
|
|
|
pbl_chunk);
|
|
|
|
if (gen_pool_add(rdev_p->pbl_pool, pbl_start, pbl_chunk, -1)) {
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s failed to add PBL chunk (%x/%x)\n",
|
|
|
|
__func__, pbl_start, pbl_chunk);
|
2008-05-07 06:03:38 +08:00
|
|
|
if (pbl_chunk <= 1024 << MIN_PBL_SHIFT) {
|
2017-02-10 06:23:48 +08:00
|
|
|
pr_warn("%s: Failed to add all PBL chunks (%x/%x)\n",
|
|
|
|
__func__, pbl_start,
|
|
|
|
rdev_p->rnic_info.pbl_top - pbl_start);
|
2008-05-07 06:03:38 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
pbl_chunk >>= 1;
|
|
|
|
} else {
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s added PBL chunk (%x/%x)\n",
|
|
|
|
__func__, pbl_start, pbl_chunk);
|
2008-05-07 06:03:38 +08:00
|
|
|
pbl_start += pbl_chunk;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
2007-02-13 08:16:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_pblpool_destroy(struct cxio_rdev *rdev_p)
|
|
|
|
{
|
|
|
|
gen_pool_destroy(rdev_p->pbl_pool);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* RQT Memory Manager. Uses Linux generic allocator.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define MIN_RQT_SHIFT 10 /* 1KB == mini RQT size (16 entries) */
|
|
|
|
#define RQT_CHUNK 2*1024*1024
|
|
|
|
|
|
|
|
u32 cxio_hal_rqtpool_alloc(struct cxio_rdev *rdev_p, int size)
|
|
|
|
{
|
|
|
|
unsigned long addr = gen_pool_alloc(rdev_p->rqt_pool, size << 6);
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s addr 0x%x size %d\n", __func__, (u32)addr, size << 6);
|
2007-02-13 08:16:18 +08:00
|
|
|
return (u32)addr;
|
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_rqtpool_free(struct cxio_rdev *rdev_p, u32 addr, int size)
|
|
|
|
{
|
2017-02-10 06:23:49 +08:00
|
|
|
pr_debug("%s addr 0x%x size %d\n", __func__, addr, size << 6);
|
2007-02-13 08:16:18 +08:00
|
|
|
gen_pool_free(rdev_p->rqt_pool, (unsigned long)addr, size << 6);
|
|
|
|
}
|
|
|
|
|
|
|
|
int cxio_hal_rqtpool_create(struct cxio_rdev *rdev_p)
|
|
|
|
{
|
|
|
|
unsigned long i;
|
|
|
|
rdev_p->rqt_pool = gen_pool_create(MIN_RQT_SHIFT, -1);
|
|
|
|
if (rdev_p->rqt_pool)
|
|
|
|
for (i = rdev_p->rnic_info.rqt_base;
|
|
|
|
i <= rdev_p->rnic_info.rqt_top - RQT_CHUNK + 1;
|
|
|
|
i += RQT_CHUNK)
|
|
|
|
gen_pool_add(rdev_p->rqt_pool, i, RQT_CHUNK, -1);
|
|
|
|
return rdev_p->rqt_pool ? 0 : -ENOMEM;
|
|
|
|
}
|
|
|
|
|
|
|
|
void cxio_hal_rqtpool_destroy(struct cxio_rdev *rdev_p)
|
|
|
|
{
|
|
|
|
gen_pool_destroy(rdev_p->rqt_pool);
|
|
|
|
}
|