On Thu, 2006-07-20 at 01:00 +0400, Alexey Kuznetsov wrote:
> Hello!
So you really do exist? I thought it was just
rumour.
> Well, if fixed point arithmetics is not a problem.
It shouldn't be. Any decimal number can be expressed
as a fraction, eg:
0.00123 = 123/10
Which can be calculate
On Wed, 2006-07-19 at 22:58 -0400, John W. Linville wrote:
> For what it is worth, there was a patch for this posted back
> in January. It stirred-up a kerfluffle, so it never got merged.
> FWIW, it touches on 802.11e QoS and multiple TX queues -- my personal
> favorite wireless subject...NOT!
>
On Wed, 2006-07-19 at 16:50 +0200, Patrick McHardy wrote:
> Please excuse my silence, I was travelling and am still catching up
> with my mails.
Sorry. Had I realised you were busy I would of
waited.
> > - As it stands, it doesn't help the qdiscs that use
> > RTAB. So unless he proposes to r
The via-velocity driver reports incorrect speed and link detected status as
viewed by ethtool (and probably other tools). This patch fixes those incorrect
reports and prettifies a long line.
Signed-off-by: Jay Cliburn <[EMAIL PROTECTED]>
--- linux-2.6.17.x86_64/drivers/net/via-velocity.c.orig
On Wed, Jul 19, 2006 at 08:49:57PM -0400, Dan Williams wrote:
> On Wed, 2006-07-19 at 10:28 -0400, Ralf Baechle wrote:
> > I got the driver to die several times under the extreme condition at the
> > KS / OLS with dozens to hundreds of other machines in the same room. The
> > last kernel message I
On Wednesday 19 July 2006 13:26, Jean-Mickael Guerin wrote:
> This patch prevents a NULL pointer dereferencing in AP mode:
> ieee80211_if_config will set conf->bssid only if device is of type STA
> or IBSS.
Why is that? Isn't there a BSSID in AP mode too? Perhaps it is calling
config_interface bef
jamal wrote:
About two more or so to complete these..
cheers,
jamal
+tc qdisc add dev lo eth0 ?
Andy.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2006-07-19 at 10:28 -0400, Ralf Baechle wrote:
> I got the driver to die several times under the extreme condition at the
> KS / OLS with dozens to hundreds of other machines in the same room. The
> last kernel message I got from about the time when wireless died was
>
> eth1: NETDEV_TX
When submitting a patch, please state what drivers you are really
changing,
your mail subject suggested a change to the dscape stack itself.
Since I look at those patches at an irregular basis, while I am always
checking for rt2x00 related patches I could have missed this one.
Especially when
Hi,
This patch prevents a NULL pointer dereferencing in AP mode:
ieee80211_if_config will set conf->bssid only if device is of type STA
or IBSS.
I see it using following commands right after module loading (with rt61)
# iwconfig wlan0 mode Master
# ifconfig wlan0 up
When submitting a patch, pl
Hello!
> Guess that Alexey wrote these RTAB lookup in a time where array lookups
> was faster... now we have that memory lookups are the bottleneck.
No, they were slower from the very beginning. If I remember correctly,
there is comment about this somewhere.
I just did not find any simple way t
Ron Mercer wrote:
Andrew,
Attached is a patch to the qla3xxx driver in your -mm test kernel. This
patch makes the following changes:
-Removed potential infinite loop in ql_sem_spinlock().
-Relaxed hardware locking granularity.
-Fixed irq_request() where shared flag was used in MSI environm
Russell Stuart wrote:
- As it stands, it doesn't help the qdiscs that use
RTAB. So unless he proposes to remove RTAB entirely the ATM patch as
it will still have to go in.
Here is a very important point here:
The RTAB (rate-table) in the kernel is NOT aligned, this is the ONLY
reason wh
Hello,
This patch prevents a NULL pointer dereferencing in AP mode:
ieee80211_if_config will set conf->bssid only if device is of type STA
or IBSS.
I see it using following commands right after module loading (with rt61)
# iwconfig wlan0 mode Master
# ifconfig wlan0 up
Signed-off-by: Jean-Mic
On Wed, 19 Jul 2006 13:01:50 -0700 (PDT)
David Miller <[EMAIL PROTECTED]> wrote:
> From: Stephen Hemminger <[EMAIL PROTECTED]>
> Date: Wed, 19 Jul 2006 15:52:04 -0400
>
> > As a related note, I am looking into fixing inet hash tables to use RCU.
>
> IBM had posted a patch a long time ago, which
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Wed, 19 Jul 2006 15:52:04 -0400
> As a related note, I am looking into fixing inet hash tables to use RCU.
IBM had posted a patch a long time ago, which would be not
so hard to munge into the current tree. See if you can
spot it in the archives :
As a related note, I am looking into fixing inet hash tables to use RCU.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Thu, 20 Jul 2006 01:30:39 +1000
> [NET]: Fix reversed error test in netif_tx_trylock
>
> A non-zero return value indicates success from spin_trylock,
> not error.
>
> Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Applied, thanks Herbert.
-
To unsubscri
Dan Williams wrote:
Actually, now that I think about it, why are _any_ applets
screen-scraping /proc/net/wireless anymore? If they profess to be a
wireless applet, yet screenscrape /proc/net/wireless, that's suspect
right there. The ioctls for status are quite well-defined and haven't
changed
I got the driver to die several times under the extreme condition at the
KS / OLS with dozens to hundreds of other machines in the same room. The
last kernel message I got from about the time when wireless died was
eth1: NETDEV_TX_BUSY returned; driver should report queue full via
ieee_device-
Sergei Shtylyov wrote:
Hello.
Jeff Garzik wrote:
It's generally not a good idea to call request_region() on an address
returned by pci_iomap(), even less so on a MMIO address. And there
was absolutely no point in claiming the region already claimed by the
PCI core, especially with the same P
There is a patch to add a debugging /proc/net/sky2/ethX interface to dump
status rings. This interface will not be part of released drivers and should
not be shipped in distribution kernels. It doesn't handle things like
device renaming and is purely released as is.
http://developer.osdl.org/shemm
Hello.
Jeff Garzik wrote:
It's generally not a good idea to call request_region() on an address
returned by pci_iomap(), even less so on a MMIO address. And there was
absolutely no point in claiming the region already claimed by the PCI
core, especially with the same PCI generic owner's name.
Sergei Shtylylov wrote:
It's generally not a good idea to call request_region() on an address returned
by pci_iomap(), even less so on a MMIO address. And there was absolutely no
point in claiming the region already claimed by the PCI core, especially with
the same PCI generic owner's name. As
John W. Linville wrote:
These patches are to be queued for 2.6.19...
---
The following changes since commit b312d799b324e895745ffe148def234fc60d5b74:
Daniel Drake:
zd1211rw: usb_clear_halt not allowed in IRQ context
are found in the git repository at:
git://git.kernel.org/pub/scm/
applied updated patch #1, and patches 2-4
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
applied
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Oumer Teyeb wrote:
Hi,
Alexey Kuznetsov wrote:
Condition triggering start of fast retransmit is the same.
The behaviour while retransmit is different. FACKless code
behaves more like NewReno.
Ok, that is a good point!! Now at least I can convince myself the
CDFs for the first retransmiss
Jouni Malinen <[EMAIL PROTECTED]> wrote:
>
> However, at least for some time, there are two different TKIP
> implementations (net/ieee80211 and net/d80211) so this would mean
> duplicating Michael MIC implementation and I would rather not do that.
Good point, let's keep it for now.
Cheers,
--
Vi
Hi,
Alexey Kuznetsov wrote:
Condition triggering start of fast retransmit is the same.
The behaviour while retransmit is different. FACKless code
behaves more like NewReno.
Ok, that is a good point!! Now at least I can convince myself the CDFs
for the first retransmissions showing that SAC
On Thu, Jul 20, 2006 at 01:39:05AM +1000, Herbert Xu wrote:
> Michael Wu <[EMAIL PROTECTED]> wrote:
> > Simplicity and consistency. Whereas the relatively simple mic part of the
> > TKIP
> > algorithm is in crypto API, the (more important, more complicated) key
> > mixing
> > part is not in cry
From: Henrik Kretzschmar <[EMAIL PROTECTED]>
Removes pci_module_init() from 56 net-subsys-drivers and replaces it with
pci_register_driver(), if the initialistion function just returns the
return value of those functions.
There are still some pci_module_init() left in the net drivers which requir
HellO!
> IsLost (SeqNum):
> This routine returns whether the given sequence number is
> considered to be lost. The routine returns true when either
> DupThresh discontiguous SACKed sequences have arrived above
> 'SeqNum' or (DupThresh * SMSS) bytes with sequence numbers greate
Michael Wu <[EMAIL PROTECTED]> wrote:
>
> Simplicity and consistency. Whereas the relatively simple mic part of the
> TKIP
> algorithm is in crypto API, the (more important, more complicated) key mixing
> part is not in crypto api. It is unlikely that either the mic or key mixing
> part would b
Ruben Puettmann <[EMAIL PROTECTED]> wrote:
>
> Yes But in the moment I thing I have not enough informations.
Oops, it was a thinko on my part.
[NET]: Fix reversed error test in netif_tx_trylock
A non-zero return value indicates success from spin_trylock,
not error.
Signed-off-by: Herbert Xu <[
Hey Folks,
I need to bind a TUN device previously created by open("/dev/net/tun",
O_RW) to a subnet, let's say 10.254.0.0/16. The ultimate goal is to have
a tunnel endpoint for a IPv4 tunnel, where I can after writing the
packet which came over the tunnel to the TUN device use an arbitary
userlan
On Mon, Jul 17, 2006 at 11:29:51PM +0200, Ulrich Kunitz wrote:
> On 06-07-16 14:17 Daniel Drake wrote:
>
> > Adrian Bunk wrote:
> > >This patch contains the following possible cleanups:
> > >- make needlessly global functions static
> > >- #if 0 unused functions
> > >
> > >Please review which of t
Hi ,
Alexey Kuznetsov wrote:
Hello!
DSACK) is used, the retransmissions seem to happen earlier .
Yes. With SACK/FACK retransmissions can be triggered earlier,
if an ACK SACKs a segment which is far enough from current snd.una.
That's what happens f.e. in T_SACK_dump5.dat
01:28:15.
Andy Furniss wrote:
> Russell Stuart wrote:
>
>> - As it stands, it doesn't help the qdiscs that use RTAB. So unless
>> he proposes to remove RTAB entirely the ATM patch as it will still
>> have to go in.
>
>
> Hmm - I was just looking at the kernel changes to htb. The only
> difference is
Russell Stuart wrote:
> On Tue, 2006-07-18 at 22:46 +0100, Andy Furniss wrote:
>
>>FWIW I think it may be possible to do it Patricks' way, as if I read it
>>properly he will end up with the ATM cell train length which gets
>>shifted by cell_log and looked up as before. The ATM length will be in
Russell Stuart wrote:
On Tue, 2006-07-18 at 22:46 +0100, Andy Furniss wrote:
FWIW I think it may be possible to do it Patricks' way, as if I read it
properly he will end up with the ATM cell train length which gets
shifted by cell_log and looked up as before. The ATM length will be in
steps o
On Tue, 2006-07-18 at 23:24 -0500, Larry Finger wrote:
> I have gotten most things working to produce wireless statistics through
> /proc/net/wireless for
> bcm43xx-d80211; however, I have one problem that I have not yet been able to
> solve. When I do a 'cat
> /proc/net/wireless', the following
Hello!
> DSACK) is used, the retransmissions seem to happen earlier .
Yes. With SACK/FACK retransmissions can be triggered earlier,
if an ACK SACKs a segment which is far enough from current snd.una.
That's what happens f.e. in T_SACK_dump5.dat
01:28:15.681050 < 192.38.55.34.51137 > 192.168.110
Hello!
> There is no socket spinlock anymore.
> Above lock is skb_queue lock which is held inside
> skb_dequeue/skb_queue_tail calls.
Lock is named differently, but it is still here.
BTW for UDP even the name is the same.
> > Equivalent of socket user lock.
>
> No, it is an equivalent for has
On Wednesday 19 July 2006 06:24, Larry Finger wrote:
> I have gotten most things working to produce wireless statistics through
> /proc/net/wireless for
> bcm43xx-d80211; however, I have one problem that I have not yet been able to
> solve. When I do a 'cat
> /proc/net/wireless', the following is
Shuya MAEDA wrote :
"while (__delta > USEC_PER_SEC){ ... }", but I think it should be
"while (__delta >= USEC_PER_SEC){ ... }". Is it right?
I agree, good catch :-)
Thanks.
--
Guillaume
In PSCHED_TADD and PSCHED_TADD2, if delta is less than tv.tv_usec (so, less
than USEC_PER_SEC too) then tv
Stefan Rompf wrote:
> VLAN devices did not get registered as admin up in 2.6.16 and IMHO also
> not in 2.6.17. So update patch description.
>
> Ok,
>
> the following patch should fix the problem. Patrick, can you give it a
> try? As the bug did not affect me through my testing, I want to be sure
Herbert Xu wrote :
Probably. Patches are welcome :)
Here are they, in both case I checked that the stuff to clear
was not already cleared, but I could not produce any misbehavior
by writing random junk instead of clearing the data. All my tests
were on the loopback using UML.
For IPv4, the adde
Hi,
> I have been quite busy lately, hence the reason for this late continuance
> of the Hardware button support for Wireless cards discussion.
> I have CC'ed the people who discussed this in earlier threads.
no problem. Look good, just one thing I'm missing:
> + For each registered hardwa
On Tue, 2006-07-18 at 23:24 -0500, Larry Finger wrote:
> I have gotten most things working to produce wireless statistics through
> /proc/net/wireless for
> bcm43xx-d80211; however, I have one problem that I have not yet been able to
> solve. When I do a 'cat
> /proc/net/wireless', the following
On Tue, 18 July 2006 23:08:01 +0400, Evgeniy Polyakov wrote:
> On Tue, Jul 18, 2006 at 02:15:17PM +0200, J?rn Engel ([EMAIL PROTECTED])
> wrote:
> >
> > Your description makes it sound as if you would take a huge leap,
> > changing all in-kernel code _and_ the userspace interface in a single
> >
On Tue, 18 Jul 2006 20:07:34 -0700, Simon Barber wrote:
> I have been thinking about a slightly different approach for the master
> device. Since the master device represents the physical hardware, I am
> thinking that the hardware driver could register the master device
> directly itself. It would
Hi David,
I am using an emualtor that I developed using netfilter (see
http://kom.aau.dk/~oumer/publications/VTC05.pdf for a description of the
emulator).. and I emualte a UMTS network with RTT of 150ms, and I use a
384kbps connection. There is UMTS frame erasure rate of 10%, but I have
persi
Hi Oumer,
Your result is interesting. Just a few questions (along with your texts):
So I looked further into the results, and what I found was that when
SACK (when I refer to SACK here, I mean SACK only without FACK and
DSACK) is used, the retransmissions seem to happen earlier .
at www.kom
Hi Stephen,
Here's another sky2 issue for you to look at when you have some time.
[EMAIL PROTECTED] reported this at http://bugs.gentoo.org/136508
but I have tried to include all relevant info here.
The connection seems to work very briefly during boot, so the user can
get an IP over DHCP. A
Hello,
Attached you can find my patch to add power managament and driver
registration to the new version of file "drivers/net/au1000_eth.c"
that implements the PHY-layer support.
Ciao,
Rodolfo Giometti
Signed-off-by: Rodolfo Giometti <[EMAIL PROTECTED]
--
GNU/Linux Solutions
Hello.
In PSCHED_TADD2, if delta is less than tv.tv_usec (so, less than
USEC_PER_SEC too) then tv_res will be before tv. The
affectation (tv_res).tv_usec = __delta; is wrong. The same applies to
PSCHED_TADD.
You are right. It is my mistake.
I think the correct fix is simply to restore the or
Could you please CC your answers to me? thanx!
Oumer Teyeb wrote:
Hi Stephen,
Thanks for the quick response.
I have done what you asked and you can find the files at
www.kom.auc.dk/~oumer/sackstuff.tar.gz
I have run the different cases 10 times each,
NT_NSACK[1-10].dat---no timestamp, no SAC
58 matches
Mail list logo
