search for: rwlock_t

...build. This is apparently due to a typo in a kernel header spinlock.h although I have not successfully modified the kernel and built zaptel against it yet. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180568 This bug report has a typo as well. It should read: #define DEFINE_RWLOCK(x) rwlock_t x = RW__LOCK_UNLOCKED make -C /lib/modules/2.6.9-34.EL/build SUBDIRS=/usr/src/zaptel-1.2.4 XPPMOD= modules make[1]: Entering directory `/usr/src/kernels/2.6.9-34.EL-i686' CC [M] /usr/src/zaptel-1.2.4/zaptel.o /usr/src/zaptel-1.2.4/zaptel.c:384: error: syntax error before "zone_lock...

...> > > > This is the key point, what system is this, and can you send me the > > > config.log > > > > This system is running Debian unstable and has the following auto* > > versions: > > I'm currently in the process of changing the setup for using rwlock_t, > not all systems have them (they are a later posix spec) and are only > used by one module (avl). > Err.. what? The rwlocks are absolutely _critical_ for icecast (though probably not for ices/libshout). You cannot remove them or make them optional. Mike <p>--- >8 ---- List a...

...one question ,that is ,when I want passup a skb to the higher protocol layer use function netif_rx ,the higher layer not response ,the skb must have not passup yet .Why ?I'm puzzling about it for some days . Sorry my english is so poor:) Thanks ! //my own bridge struct struct Bridge{ rwlock_t lock; rwlock_t hash_lock; struct net_device dev; struct Bridge_fdb_entry *hash[BR_HASH_SIZE]; }; extern struct Bridge *brg; //the bridge initiation , will be called in module_init struct Bridge *Bridge_fdb_init() { struct Bridge *br; if ((br = kmalloc(sizeof(*br),GFP_KERNEL)) == NULL) retu...

On 13 Mar 2003, Karl Heyes wrote: > > ../thread/thread.h:90: syntax error before "pthread_rwlock_t" > > This is the key point, what system is this, and can you send me the > config.log This system is running Debian unstable and has the following auto* versions: automake (GNU automake) 1.4-p6 autoconf (GNU Autoconf) 2.57 Unstable has automake 1.4, 1.5, 1.6 and 1.7 available. Is...

...s/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c > index 613b18001a0c..6058b07fea08 100644 > --- a/drivers/s390/virtio/virtio_ccw.c > +++ b/drivers/s390/virtio/virtio_ccw.c > @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; > > struct airq_info { > rwlock_t lock; > - u8 summary_indicator; > + u8 summary_indicator_idx; > struct airq_struct airq; > struct airq_iv *aiv; > }; > static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; > +static u8 *summary_indicators; > + > +static inline u8 *get_summary_indicator(struct ai...

...s/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c > index 613b18001a0c..6058b07fea08 100644 > --- a/drivers/s390/virtio/virtio_ccw.c > +++ b/drivers/s390/virtio/virtio_ccw.c > @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; > > struct airq_info { > rwlock_t lock; > - u8 summary_indicator; > + u8 summary_indicator_idx; > struct airq_struct airq; > struct airq_iv *aiv; > }; > static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; > +static u8 *summary_indicators; > + > +static inline u8 *get_summary_indicator(struct ai...

...can/j1939/j1939-priv.h b/net/can/j1939/j1939-priv.h index 16af1a7f80f6..74f15592d170 100644 --- a/net/can/j1939/j1939-priv.h +++ b/net/can/j1939/j1939-priv.h @@ -86,7 +86,7 @@ struct j1939_priv { unsigned int tp_max_packet_size; /* lock for j1939_socks list */ - spinlock_t j1939_socks_lock; + rwlock_t j1939_socks_lock; struct list_head j1939_socks; struct kref rx_kref; diff --git a/net/can/j1939/main.c b/net/can/j1939/main.c index ecff1c947d68..a6fb89fa6278 100644 --- a/net/can/j1939/main.c +++ b/net/can/j1939/main.c @@ -274,7 +274,7 @@ struct j1939_priv *j1939_netdev_start(struct net_devi...

Hi Guys, Im having a problem compiling zaptel 1.2.4 on CentOS 4.3, anyone encountered this problem before? Here's the error i got: make -C /lib/modules/2.6.9-34.EL/build SUBDIRS=/usr/src/zaptel-1.2.4 XPPMOD= modules make[1]: Entering directory `/usr/src/kernels/2.6.9-34.EL-i686' CC [M] /usr/src/zaptel-1.2.4/zaptel.o /usr/src/zaptel-1.2.4/zaptel.c:384: error: syntax error before

Hi Guys, Im having a problem compiling zaptel 1.2.4 on CentOS 4.3, anyone encountered this problem before? Here's the error i got: make -C /lib/modules/2.6.9-34.EL/build SUBDIRS=/usr/src/zaptel-1.2.4 XPPMOD= modules make[1]: Entering directory `/usr/src/kernels/2.6.9-34.EL-i686' CC [M] /usr/src/zaptel-1.2.4/zaptel.o /usr/src/zaptel-1.2.4/zaptel.c:384: error: syntax error before

...2003-03-13 at 23:28, Geoff Shang wrote: > > This is the key point, what system is this, and can you send me the > > config.log > > This system is running Debian unstable and has the following auto* > versions: I'm currently in the process of changing the setup for using rwlock_t, not all systems have them (they are a later posix spec) and are only used by one module (avl). The configure found the right flags to use but the make didn't use it, so maybe try the recent checkins and if it's still a problem then send me the config.log and libshout/avl/Makefile > au...

...), 7 deletions(-) diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c index 613b18001a0c..6058b07fea08 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; struct airq_info { rwlock_t lock; - u8 summary_indicator; + u8 summary_indicator_idx; struct airq_struct airq; struct airq_iv *aiv; }; static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; +static u8 *summary_indicators; + +static inline u8 *get_summary_indicator(struct airq_info *info) +{ + return summary_indicators + i...

...), 7 deletions(-) diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c index 03c9f7001fb1..f666ed397dc0 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; struct airq_info { rwlock_t lock; - u8 summary_indicator; + u8 summary_indicator_idx; struct airq_struct airq; struct airq_iv *aiv; }; static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; +static u8 *summary_indicators; + +static inline u8 *get_summary_indicator(struct airq_info *info) +{ + return summary_indicators + i...

...), 7 deletions(-) diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c index 03c9f7001fb1..efebd6dcd124 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; struct airq_info { rwlock_t lock; - u8 summary_indicator; + u8 summary_indicator_idx; struct airq_struct airq; struct airq_iv *aiv; }; static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; +static u8 *summary_indicators; + +static inline u8 *get_summary_indicator(struct airq_info *info) +{ + return summary_indicators + i...

...), 8 deletions(-) diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c index e5e10aa54aa1..fe46079f105e 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; struct airq_info { rwlock_t lock; - u8 summary_indicator; + u8 summary_indicator_idx; struct airq_struct airq; struct airq_iv *aiv; }; static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; +static u8 *summary_indicators; + +static inline u8 *get_summary_indicator(struct airq_info *info) +{ + return summary_indicators + i...

...), 8 deletions(-) diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c index 800252955a2f..1a55e5942d36 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; struct airq_info { rwlock_t lock; - u8 summary_indicator; + u8 summary_indicator_idx; struct airq_struct airq; struct airq_iv *aiv; }; static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; +static u8 *summary_indicators; + +static inline u8 *get_summary_indicator(struct airq_info *info) +{ + return summary_indicators + i...

...gt;> b/drivers/s390/virtio/virtio_ccw.c >> index 613b18001a0c..6058b07fea08 100644 >> --- a/drivers/s390/virtio/virtio_ccw.c >> +++ b/drivers/s390/virtio/virtio_ccw.c >> @@ -140,11 +140,17 @@ static int virtio_ccw_use_airq = 1; >> ? struct airq_info { >> ????? rwlock_t lock; >> -??? u8 summary_indicator; >> +??? u8 summary_indicator_idx; >> ????? struct airq_struct airq; >> ????? struct airq_iv *aiv; >> ? }; >> ? static struct airq_info *airq_areas[MAX_AIRQ_AREAS]; >> +static u8 *summary_indicators; >> + >> +s...

Greetings, I have just updated our test server to 2.6.9-34.EL and get the following error messages when compiling zaptel: make[1]: Entering directory `/usr/src/kernels/2.6.9-34.EL-i686' CC [M] /usr/src/zaptel/zaptel-1.2.1/zaptel.o /usr/src/zaptel/zaptel-1.2.1/zaptel.c:383: error: syntax error before "zone_lock" /usr/src/zaptel/zaptel-1.2.1/zaptel.c:383: warning: type defaults

...ions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use atomic variables to avoid taking t_handle_lock in jbd2_journal_stop jbd2: Change j_state_lock to be a rwlock_t jbd2: Remove t_handle_lock from start_this_handle() fs/ext4/inode.c | 4 +- fs/ext4/super.c | 4 +- fs/jbd2/checkpoint.c | 18 +++--- fs/jbd2/commit.c | 42 ++++++------ fs/jbd2/journal.c | 94 +++++++++++++-------------- fs/jbd2/transaction.c | 172 ++++++++++...

...} diff -Nru a/net/bridge/br_private.h b/net/bridge/br_private.h --- a/net/bridge/br_private.h 2004-07-28 15:30:04 -07:00 +++ b/net/bridge/br_private.h 2004-07-28 15:30:04 -07:00 @@ -86,7 +86,7 @@ struct list_head port_list; struct net_device *dev; struct net_device_stats statistics; - rwlock_t hash_lock; + spinlock_t hash_lock; struct hlist_head hash[BR_HASH_SIZE]; struct list_head age_list; @@ -136,8 +136,10 @@ extern void br_fdb_cleanup(unsigned long arg); extern void br_fdb_delete_by_port(struct net_bridge *br, struct net_bridge_port *p); +extern struct net_bridge...

Hi, here's the guest driver support for adapter interrupts in virtio-ccw. We use one summary indicator per page of indicators. For each device, we try to find a space in an indicator where all of its virtqueues fit. Locking probably needs some more love, but it seems to work fine so far. Cornelia Huck (2): KVM: s390: virtio-ccw: Handle command rejects. KVM: s390: virtio-ccw adapter