(This patch was originally sent as part of the patch series that converted
drivers using ieee80211.h to d80211.h. This patch is still valid because
ray_cs does not need ieee80211.h - it needs iw_handler.h. The dependency on
ieee80211.h was added as part of a build fix patch following the merge
From: Heiko Carstens [EMAIL PROTECTED]
qeth: bhs must be disabled when accessing neighbour tables.
=
[ INFO: inconsistent lock state ]
-
inconsistent {in-softirq-W} - {softirq-on-W} usage.
modprobe/529 [HC0[0]:SC0[0]:HE1:SE1] takes:
On Mon, Aug 14, 2006 at 07:04:01AM +0200, Andi Kleen wrote:
Another reason to move it in the sk_buff would be better cache
coloring? Currently on large/small MTU packets it will be always on
the same colors.
If we went with a fully paged skbs this should be a non-issue, right?
In a fully
Generic event handling mechanism.
Changes from 'take8' patchset:
* fixed mmap release bug
* use module_init() instead of late_initcall()
* use better structures for timer notifications
Changes from 'take7' patchset:
* new mmap interface (not tested, waiting for other changes to be acked)
Core files.
This patch includes core kevent files:
- userspace controlling
- kernelspace interfaces
- initialization
- notification state machines
Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED]
diff --git a/arch/i386/kernel/syscall_table.S b/arch/i386/kernel/syscall_table.S
index
Core files.
This patch includes core kevent files:
- userspace controlling
- kernelspace interfaces
- initialization
- notification state machines
Signed-off-by: Evgeniy Polyakov [EMAIL PROTECTED]
diff --git a/arch/i386/kernel/syscall_table.S b/arch/i386/kernel/syscall_table.S
index
poll/select() notifications. Timer notifications.
This patch includes generic poll/select and timer notifications.
kevent_poll works simialr to epoll and has the same issues (callback
is invoked not from internal state machine of the caller, but through
process awake).
Timer notifications can
On Sun, 2006-08-13 at 22:22 -0700, Andrew Morton wrote:
On Mon, 14 Aug 2006 07:03:55 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
On Sun, 2006-08-13 at 21:58 -0700, Andrew Morton wrote:
On Mon, 14 Aug 2006 06:40:53 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
Testcase:
On Mon, 2006-08-14 at 09:13 +0400, Evgeniy Polyakov wrote:
On Sun, Aug 13, 2006 at 01:16:15PM -0700, Daniel Phillips ([EMAIL PROTECTED])
wrote:
Indeed. The rest of the corner cases like netfilter, layered protocol and
so on need to be handled, however they do not need to be handled right
On Mon, Aug 14, 2006 at 08:45:43AM +0200, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
Just for clarification - it will be completely impossible to login using
openssh or some other priveledge separation protocol to the machine due
to the nature of unix sockets. So you will be unable to
Michael Ellerman wrote:
On Sat, 2006-08-12 at 07:40 +1000, Anton Blanchard wrote:
Hi,
drivers/net/ehea/ehea.h| 452
+#define EHEA_DRIVER_NAME IBM eHEA
You are using this for ethtool get_drvinfo. Im not sure if it should
match the module name, and I worry about having a space in the
On Sat, Aug 12, 2006 at 12:10:35PM -0700, Ulrich Drepper wrote:
Suparna Bhattacharya wrote:
I am wondering about that too. IIRC, the IO_NOTIFY_* constants are not
part of the ABI, but only internal to the kernel implementation. I think
Zach had suggested inferring THREAD_ID notification if
On Mon, 14 Aug 2006 08:45:40 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
On Sun, 2006-08-13 at 22:22 -0700, Andrew Morton wrote:
On Mon, 14 Aug 2006 07:03:55 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
On Sun, 2006-08-13 at 21:58 -0700, Andrew Morton wrote:
On Mon, 14 Aug 2006
On Monday August 14, [EMAIL PROTECTED] wrote:
On Sun, 2006-08-13 at 22:22 -0700, Andrew Morton wrote:
We could track dirty anonymous memory and throttle.
Also, there must be some value of /proc/sys/vm/min_free_kbytes at which a
machine is no longer deadlockable with any of these
On Mon, Aug 14, 2006 at 05:17:29PM +1000, Neil Brown ([EMAIL PROTECTED]) wrote:
Would it be too much waste to reserve one page for every idle socket?
Does this have some fatal flaw?
Yep, in some cases number of sockets is unlimited, but number of total
memory they can eat is limited already
On Monday 14 August 2006 09:29, Herbert Xu wrote:
On Mon, Aug 14, 2006 at 07:04:01AM +0200, Andi Kleen wrote:
Another reason to move it in the sk_buff would be better cache
coloring? Currently on large/small MTU packets it will be always on
the same colors.
If we went with a fully
On Mon, Aug 14, 2006 at 09:45:53AM +0200, Andi Kleen wrote:
Even for 1.5k MTU? (which is still the most common case after all)
Ideally they would stay in kmalloc memory. Could you explain the cache
colouring problem for 1500-byte packets?
Cheers,
--
Visit Openswan at
Michael Wu wrote:
+ WLAN_EID_QUIET = 40,
I was about to send a patch fixing this as well :)
+ WLAN_EID_IBSS_DFS = 41,
/* EIDs defined as part fo 11h - ends */
Care to fix the two occurrences of this typo in a respun patch? (should
be 'of' instead of 'fo')
If you can't easily
On Sun, Aug 13, 2006 at 05:04:31PM +0400, Alexey Kuznetsov ([EMAIL PROTECTED])
wrote:
Hello!
E1000 wants 16K buffers for jumbo MTU settings.
The reason is that the chip can only handle power-of-2 buffer
sizes, and next hop from 9K is 16K.
Let it use pages. Someone should start. :-)
This mail is supposed to just serve as a thread parent for a bunch of
questions, small patches and observations I made playing with d80211 and
looking through the source code over the weekend. Just so you can ignore
the whole thread if you don't care :)
johannes
-
To unsubscribe from this
I'd like to see a link from the wiphy to the master interface that
belongs to it so one can tell this easily on systems that have multiple
wireless devices. wpa_supplicant could use this, I guess. I think
another link to wlan#ap should be created (or does wpa_supplicant set
the name of that so
This patch fixes places where pointers are compared against 0 and
unifies it a bit.
Signed-off-by: Johannes Berg [EMAIL PROTECTED]
--- wireless-dev.orig/net/d80211/ieee80211_scan.c2006-08-12
10:11:21.069644280 +0200
+++ wireless-dev/net/d80211/ieee80211_scan.c2006-08-12
Somewhere, sometime, someone had to start getting rid of bitfields ;)
This one seemed an easy target :P
Signed-off-by: Johannes Berg [EMAIL PROTECTED]
--- wireless-dev.orig/net/d80211/wme.c2006-08-12 10:43:01.809644280
+0200
+++ wireless-dev/net/d80211/wme.c2006-08-12
I think we need to get rid of this parameter and if really necessary
have this information passed from the lowlevel driver to the stack.
johannes
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Friday 11 August 2006 08:45, you wrote:
From: Krzysztof Oledzki [EMAIL PROTECTED]
Date: Thu, 10 Aug 2006 20:18:23 +0200 (CEST)
OK, this patch really solves the bug from my report. Are there any
chances for similar fix in the net-2.6.19.git?
I'm still thinking about this patch and what
On Monday 14 August 2006 09:50, Herbert Xu wrote:
On Mon, Aug 14, 2006 at 09:45:53AM +0200, Andi Kleen wrote:
Even for 1.5k MTU? (which is still the most common case after all)
Ideally they would stay in kmalloc memory. Could you explain the cache
colouring problem for 1500-byte
For whatever reason, nm always thinks that my default wlan0 device is a
*wired* device. I do wonder where the bug is, but couldn't pinpoint it
yet, any ideas? mm version is 0.6.3. I'd have thought it would go by the
presence of wireless extensions, but if so it uses some call to detect
it that
Hey,
I was looking through the d80211 code and noticed this comment and code:
/* TODO: sta_aid could be replaced by 2008-bit large bitfield of
* that could be used in TIM element generation. This would also
* make TIM element generation a bit faster. */
/* AID
... is a big mess.
What's with all the comments saying 'maybe with blabla hardware that can
be done in hw but disable here now' etc? Can't we just have a 'please
decide' callback in the driver that tells us whether this can be done in
hw or sw?
Or how about no_tkip_wmm_hwaccel? That seems
As far as I understand the entire point of the wlan#ap interface is to
receive all management relevant management frames. (If that's wrong, reply
now and don't read the rest)
Hence, I think it ought to be named 'wlan#mgmt' instead. However, I think
it's hard-coded existence is bogus.
How about
BTW, I'll be honest with you, by continuing to bug me about this, it
makes me want to look at this issue less, not more.
Just be patient ok?
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
From: Christophe Devriese [EMAIL PROTECTED]
Date: Mon, 14 Aug 2006 10:16:36 +0200
On Friday 11 August 2006 08:45, you wrote:
From: Krzysztof Oledzki [EMAIL PROTECTED]
Date: Thu, 10 Aug 2006 20:18:23 +0200 (CEST)
OK, this patch really solves the bug from my report. Are there any
Hi,
...
(Meanwhile, Michal, can I get a Signed-off-by: line from you for these
patches? Thanks a lot.)
no problem :-)
There is a leak of a socket's multicast source filter list structure
on closing a socket with a multicast source filter set on an interface
that does not exist any more.
On Tue, Aug 08, 2006 at 02:38:51PM +0300, Pekka Pietikainen wrote:
Hmm... I retried with a 2.6.18rc4-based rawhide kernel and the warning
is still there, previous one was rc3-git7.
Could be http://marc.theaimsgroup.com/?l=linux-netdevm=115461336523555w=2
which isn't upstream yet, right?
The
[23750.726463] NETDEV WATCHDOG: wmaster0: transmit timed out
[23750.726482] wmaster0: resetting interface.
[23750.726490] bcm43xx_d80211: Controller RESET (IEEE reset) ...
[23750.753458] bcm43xx_d80211: select_wireless_core: cleanup
[23750.753477] bcm43xx_d80211: Radio turned off
[23750.753538]
On Mon, 2006-08-14 at 00:07 -0700, Andrew Morton wrote:
On Mon, 14 Aug 2006 08:45:40 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
On Sun, 2006-08-13 at 22:22 -0700, Andrew Morton wrote:
On Mon, 14 Aug 2006 07:03:55 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
On Sun,
From: Andrew Morton [EMAIL PROTECTED]
Date: Mon, 14 Aug 2006 00:07:36 -0700
What is a socket wait queue and how/why can it consume so much memory?
Can it be prevented from doing that?
If this refers to the socket buffers, they're mostly allocated with
at least __GFP_WAIT, aren't they?
On Mon, Aug 14, 2006 at 10:15:52AM +0200, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
If this refers to the socket buffers, they're mostly allocated with
at least __GFP_WAIT, aren't they?
Wherever it is that packets go if the local end is tied up and cannot
accept them instantly. The simple
On Mon, 2006-08-14 at 12:25 +0400, Evgeniy Polyakov wrote:
On Mon, Aug 14, 2006 at 10:15:52AM +0200, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
If this refers to the socket buffers, they're mostly allocated with
at least __GFP_WAIT, aren't they?
Wherever it is that packets go if the
Hello.
Network tree allocator can be used to allocate memory for all network
operations from any context. Main designed features are:
* reduced fragmentation (self defragmentation)
* possibility to create zero-copy sending and receiving (ground work
for userspace netchannels and
From: Evgeniy Polyakov [EMAIL PROTECTED]
Date: Mon, 14 Aug 2006 15:04:03 +0400
/* These elements must be at the end, see alloc_skb() for details. */
- unsigned inttruesize;
+ unsigned inttruesize, __tsize;
There is no real need for new member.
-
On Sat, 12 August 2006 06:56:24 +1000, Anton Blanchard wrote:
+
+ skb_index = ((index - i
+ + port_res-skb_arr_sq_len)
+% port_res-skb_arr_sq_len);
This is going to force an
On Mon, Aug 14, 2006 at 04:22:06AM -0700, David Miller ([EMAIL PROTECTED])
wrote:
From: Evgeniy Polyakov [EMAIL PROTECTED]
Date: Mon, 14 Aug 2006 15:04:03 +0400
/* These elements must be at the end, see alloc_skb() for details. */
- unsigned inttruesize;
+ unsigned
Evgeniy Polyakov [EMAIL PROTECTED] writes:
Design notes.
Original idea was to store meta information used for allocation in an
AVL tree [1], but since I found a way to use some unused fields in struct
page,
tree is unused in the allocator.
But there seems to be still an AVL tree in there?
On Mon, 2006-08-14 at 10:18 +0200, Johannes Berg wrote:
For whatever reason, nm always thinks that my default wlan0 device is a
*wired* device. I do wonder where the bug is, but couldn't pinpoint it
yet, any ideas? mm version is 0.6.3. I'd have thought it would go by the
presence of
Dan Williams wrote:
No, it asks HAL what the device type is actually. HAL looks for the
interface in /proc/net/wireless currently, and if it's not there, says
the device is wired. Run 'lshal', look for your wlan device, and see if
info.capabilities includes 'net.80211'.
Yeah, I noticed it
Johannes Berg wrote:
Dan Williams wrote:
Yeah, I noticed it wasn't in /proc/net/wireless. Should've tipped me off
I guess. And I probably also should've thought that nm would ask HAL.
Looks like I wasn't really on track when I wrote this yesterday ;)
So if the wlanX interface isn't in
Larry Finger wrote:
The RFCd patch to add wireless stats to d80211 received only minor
comments, which have all been addressed. I will be submitting a proper
patch to Linville's tree today. In addition, I have reached an
agreement with the authors of all other drivers that use d80211 on a
Hi
Anton Blanchard wrote:
What is going to be done about the debug infrastructure in the ehea
driver? The entry and exit traces really need to go, and any other debug
you think is important to users needs to go into debugfs or something
similar.
I see a similar issue in the ehca driver that I
Johannes Berg wrote:
-if (!local-hw-passive_scan) {
+if (local-hw-passive_scan == NULL) {
Alright, this is icky. I'll make another pass and change it all to if
(x) or if (!x) instead of comparing to NULL. Don't hold your breath
though, earliest next weekend.
johannes
-
To
Hello!
e1000 will setup head/data/tail pointers to point to the area in the
first sg page.
Maybe.
But I still hope this is not necessary, the driver should be able to do
at least primitive header splitting, in that case the header could
be inlined to skb.
Alternatively, header can be copied
This patch implements wireless statistics for bcm43xx using the d80211 stack.It
also sets a framework for the implementation in other drivers that use the
d80211 code. The component parts have been circulated on the netdev mailing
list, and all suggested changes have been incorporated. The
On Mon, Aug 14, 2006 at 05:19:19PM +0400, Alexey Kuznetsov ([EMAIL PROTECTED])
wrote:
What if we will store array of pages and in shared info
just like we have right now. So there will only one destructor.
Seems, this is not enough. Actually, I was asking for your experience
with aio.
On Mon, Aug 14, 2006 at 01:40:21PM +0200, Andi Kleen ([EMAIL PROTECTED]) wrote:
Evgeniy Polyakov [EMAIL PROTECTED] writes:
Design notes.
Original idea was to store meta information used for allocation in an
AVL tree [1], but since I found a way to use some unused fields in struct
page,
Evgeniy Polyakov (on Mon, 14 Aug 2006 15:04:03 +0400) wrote:
Network tree allocator can be used to allocate memory for all network
operations from any context
...
Design of allocator allows to map all node's pages into userspace thus
allows to have true zero-copy support for both sending and
Evgeniy Polyakov wrote:
On Sun, Aug 13, 2006 at 05:42:47PM -0700, Daniel Phillips ([EMAIL PROTECTED])
wrote:
As for sk_buff cow break, we need to look at which network paths do it
(netfilter obviously, probably others) and decide whether we just want
to declare that the feature breaks
On Mon, Aug 14, 2006 at 10:07:48PM +1000, Keith Owens (kaos@ocs.com.au) wrote:
Evgeniy Polyakov (on Mon, 14 Aug 2006 15:04:03 +0400) wrote:
Network tree allocator can be used to allocate memory for all network
operations from any context
...
Design of allocator allows to map all node's
On Mon, 2006-08-14 at 15:04 +0400, Evgeniy Polyakov wrote:
Defragmentation is a part of freeing algorithm and initial fragmentation
avoidance is being done at allocation time by removing power-of-two
allocations. Rate of fragmentation can be found in some userspace
modlling tests being done
Here's the patch I used to find out which tasklet was giving me a hard
time with bcm43xx and d80211. I don't really expect this to be applied
anywhere but didn't want to sit on it either.
Signed-off-by: Johannes Berg [EMAIL PROTECTED]
--- wireless-dev.orig/include/linux/interrupt.h
On Mon, Aug 14, 2006 at 02:25:13PM +0200, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
On Mon, 2006-08-14 at 15:04 +0400, Evgeniy Polyakov wrote:
Defragmentation is a part of freeing algorithm and initial fragmentation
avoidance is being done at allocation time by removing power-of-two
On Mon, Aug 14, 2006 at 04:35:30PM +0400, Evgeniy Polyakov ([EMAIL PROTECTED])
wrote:
I'm still not clear on how you want to do this, only the trivial case of
a sniffer was mentioned by you. To be able to do true zero-copy receive
each packet will have to have its own page(s). Simply
Rik van Riel [EMAIL PROTECTED] wrote:
That should not be any problem, since skb's (including cowed ones)
are short lived anyway. Allocating a little bit more memory is
fine when we have a guarantee that the memory will be freed again
shortly.
I'm not sure about the context the comment
Hey,
In my seemingly never-ending quest to actually use the d80211 stack for
something useful I just wanted to write a small setuid tool that:
* creates and opens a new monitor interface
* drops priviledges
* ... does things with received frames ... (not interesting for this
discussion)
*
Michael Ellerman wrote:
--- linux-2.6.18-rc4-orig/drivers/net/ehea/ehea.h 1969-12-31
16:00:00.0 -0800
+++ kernel/drivers/net/ehea/ehea.h 2006-08-08 23:59:39.927452928 -0700
+
+#define EHEA_PAGESHIFT 12
+#define EHEA_PAGESIZE 4096UL
+#define EHEA_CACHE_LINE 128
This looks
Hi
Anton Blanchard wrote:
Hi,
--- linux-2.6.18-rc4-orig/drivers/net/ehea/ehea_phyp.c 1969-12-31
16:00:00.0 -0800
+u64 ehea_h_alloc_resource_eq(const u64 hcp_adapter_handle,
...
+u64 hipz_h_reregister_pmr(const u64 adapter_handle,
...
+static inline int
On Mon, 2006-08-14 at 10:12 +0200, Johannes Berg wrote:
I'd like to see a link from the wiphy to the master interface that
belongs to it so one can tell this easily on systems that have multiple
wireless devices. wpa_supplicant could use this, I guess. I think
another link to wlan#ap should
Johannes Berg wrote:
Hence, I think it ought to be named 'wlan#mgmt' instead.
I see it's actually called wmgmt# now. Sorry. The rest of this mail
still holds though.
johannes
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More
jamal wrote:
Folks,
I am not a big readability officianado, but this piece of code has
become a victim of hairy activities over the last few years. So while i
was furiously chasing Herbert's qdisc_is_running changes[1] i made a
small cleanup just so that i could absorb what was going on.
The
Past Due Invoice Attached
invoice.doc
Description: MS-Word document
On Mon, Aug 14, 2006 at 03:20:58PM +0200, Johannes Berg wrote:
Johannes Berg wrote:
-if (!local-hw-passive_scan) {
+if (local-hw-passive_scan == NULL) {
Alright, this is icky. I'll make another pass and change it all to if
(x) or if (!x) instead of comparing to NULL. Don't hold
On Mon, Aug 14, 2006 at 10:16:53AM +0200, Johannes Berg wrote:
... is a big mess.
Yes, and so is the number of different ways this has been implemented in
hardware designs..
What's with all the comments saying 'maybe with blabla hardware that can
be done in hw but disable here now' etc?
On Mon, Aug 14, 2006 at 10:22:34AM +0200, Johannes Berg wrote:
As far as I understand the entire point of the wlan#ap interface is to
receive all management relevant management frames. (If that's wrong, reply
now and don't read the rest)
Hence, I think it ought to be named 'wlan#mgmt'
Jouni Malinen wrote:
How about we just add a new interface mode called MGT_MONITOR and
wpa_supplicant simply creates a new device via the regular sysfs mechanism,
and then sets that MGT_MONITOR mode via the relevant WEXT ioctl? iwconfig
doesn't even need to be taught about this mode except for
On Mon, Aug 14, 2006 at 10:15:14AM +0200, Johannes Berg wrote:
Somewhere, sometime, someone had to start getting rid of bitfields ;)
Yes and you wouldn't believe how many times I have had to complain about
this particular case internally with it always coming back as bitfield
even after showing
On Monday 14 August 2006 00:54, Johannes Berg wrote:
+ WLAN_EID_IBSS_DFS = 41,
/* EIDs defined as part fo 11h - ends */
Care to fix the two occurrences of this typo in a respun patch? (should
be 'of' instead of 'fo')
If you can't easily recreate that patch I'll send one after this goes
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
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
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
Jim Lewis wrote:
This patch adds ethtool -g (show ring sizes) support to the Spidernet
network driver.
Signed-off-by: James K Lewis [EMAIL PROTECTED]
ACK, but does not apply:
Applying 'Patch to add ethtool -g to Spidernet network driver'
error: patch fragment without header at line 13: @@
Andrew Morton wrote:
I have a really large pile of patches to send out to the subsystem
maintainers, so this'll be coming back at you soon via that route.
Great, I had hoped that might be the case.
Thanks,
Jeff
-
To unsubscribe from this list: send the line unsubscribe netdev in
On Mon, 14 Aug 2006 14:02:26 -0400
Jeff Garzik [EMAIL PROTECTED] wrote:
Jim Lewis wrote:
This patch adds ethtool -g (show ring sizes) support to the Spidernet
network driver.
Signed-off-by: James K Lewis [EMAIL PROTECTED]
ACK, but does not apply:
I added it to rc4-mm1. I
This patch adds the necessary bits to the adm8211 and rt2x00 family of drivers
for them to report wireless statistics to the d80211 stack in the wireless-dev
tree. At present as discussed with Ivo van Doorn (rt2x00) and Michael Wu
(adm2311), the needed values of maxssi, noise and signal are
The purpose of the wlap0ap or wlap0mgmt interface is to communicate
between hostapd/wpa_supplicant and the kernel. What travels over this
interface is not quite pure 802.11 management frames - there is some
meta-data with each frame, and a few special case messages. E.G.
transmitted frames are
On Wed, Aug 09, 2006 at 04:13:25PM -0500, Larry Finger wrote:
This patch removes the ugly TODO output from the logs for bcm43xx-softmac.
The
patch is for the latest version of Linville's wireless-2.6 tree.
I'm not sure if this is the right approach. In fact I know it isn't --
the right
On Sat, Aug 12, 2006 at 05:59:46PM +0100, Daniel Drake wrote:
+ /* All of these writes are identical to AL2230 unless otherwise
+ * specified */
+ static const struct zd_ioreq16 ioreqs_1[] = {
+ /* This one is 7230-specific, and happens before the rest */
+
John W. Linville wrote:
On Sat, Aug 12, 2006 at 05:59:46PM +0100, Daniel Drake wrote:
+ /* All of these writes are identical to AL2230 unless otherwise
+* specified */
+ static const struct zd_ioreq16 ioreqs_1[] = {
+ /* This one is 7230-specific, and happens
On Monday 14 August 2006 20:55, John W. Linville wrote:
On Wed, Aug 09, 2006 at 04:13:25PM -0500, Larry Finger wrote:
This patch removes the ugly TODO output from the logs for bcm43xx-softmac.
The
patch is for the latest version of Linville's wireless-2.6 tree.
I'm not sure if this is
Hello!
Let one Linux box have two interfaces to 2 different IPv4 networks,
and for some IP both networks have the host with this IP address,
e.g. for an address from RFC1918.
Or even both use the same IPv4 address block.
We can say that one IP from the first network
and numerically the same
The following changes since commit e9ffb3d7ec94083a44a8721681391beca2ffd68c:
John W. Linville:
Merge branch 'from-linus' into upstream
are found in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
upstream
Daniel Drake:
zd1211rw:
From: Stephen Hemminger [EMAIL PROTECTED]
Date: Tue, 15 Aug 2006 07:42:39 -0700
Please don't change the values because some older drvers still return 1
rather
than NETDEV_TX_BUSY
Unfortunately, this is probably very true. So we indeed cannot
change the NETDEV_TX_BUSY value.
-
To unsubscribe
Change the top level list of neighbor tables to use RCU.
Minor change to BUG() if a neighbor table is registered twice.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
---
include/net/neighbour.h |2 -
net/core/neighbour.c| 89 ++--
2
The reading of the contents of a neighbour entry can be converted
from a slow reader/writer lock to a fast lockless sequence number check.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
---
include/net/neighbour.h |2
net/core/neighbour.c| 102
This set of patches changes the neighbour table used by ARP and
IPV6 neighbour discovery to use RCU and seqlock's. This improves
performance by eliminated locked instructions in the common
case.
--
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to
Change the pneigh_entry table to hlist from list.h
to allow for easier later conversion to RCU.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
---
include/net/neighbour.h |6 ++--
net/core/neighbour.c| 58
2 files changed, 33
The function neigh_update_hhs is only used in neighbour.c
and let compiler decide to inline or not.
There are several symbols only used by rtnetlink and since it can
not be a module, there is no reason to export them.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
---
net/core/neighbour.c
Change the neighbour table hash list to hlist from list.h
to allow for easier later conversion to RCU.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
---
include/net/neighbour.h |6 -
net/core/neighbour.c| 160 +---
2 files changed, 88
Use RCU to allow for lock less access to the neighbour table.
This should speedup the send path because no atomic operations
will be needed to lookup ARP entries, etc.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
---
include/net/neighbour.h |4 -
net/core/neighbour.c| 158
Signed-off-by: Thomas Graf [EMAIL PROTECTED]
Index: net-2.6.19.git/include/linux/rtnetlink.h
===
--- net-2.6.19.git.orig/include/linux/rtnetlink.h
+++ net-2.6.19.git/include/linux/rtnetlink.h
@@ -584,6 +584,7 @@ struct rtnetlink_link
This patchset reworks rtnetlink notifications. Notification logic
is fixed and gets hidden behind nlmsg_notify() and the rtnl socket
is no longer directly accessed. All notification paths get
appropriate error handling. NLM_F_ECHO support is added where it
makes sense and no major surgery is
Signed-off-by: Thomas Graf [EMAIL PROTECTED]
Index: net-2.6.19.git/net/core/wireless.c
===
--- net-2.6.19.git.orig/net/core/wireless.c
+++ net-2.6.19.git/net/core/wireless.c
@@ -85,6 +85,7 @@
#include linux/wireless.h
1 - 100 of 167 matches
Mail list logo
