<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/linux/netpoll.h, branch linux-2.6.15.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.15.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.15.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2005-10-12T22:12:21Z</updated>
<entry>
<title>[NETPOLL]: wrong return for null netpoll_poll_lock()</title>
<updated>2005-10-12T22:12:21Z</updated>
<author>
<name>Ben Dooks</name>
</author>
<published>2005-10-12T22:12:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=afb997c6163b33292d31a09d6aa5cbb03ffa5bf1'/>
<id>urn:sha1:afb997c6163b33292d31a09d6aa5cbb03ffa5bf1</id>
<content type='text'>
When netpoll is not being used, the macro that
defines the removed routing netpoll_poll_lock
defines the return as zero, but the real
routine returns a `void *`

Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[NETPOLL]: fix initialization/NAPI race</title>
<updated>2005-08-12T02:27:43Z</updated>
<author>
<name>Matt Mackall</name>
</author>
<published>2005-08-12T02:27:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=53fb95d3c14290fd6ee808b221e35493f096246f'/>
<id>urn:sha1:53fb95d3c14290fd6ee808b221e35493f096246f</id>
<content type='text'>
This fixes a race during initialization with the NAPI softirq
processing by using an RCU approach.

This race was discovered when refill_skbs() was added to
the setup code.

Signed-off-by: Matt Mackall &lt;mpm@selenic.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[NETPOLL]: add retry timeout</title>
<updated>2005-08-12T02:25:54Z</updated>
<author>
<name>Matt Mackall</name>
</author>
<published>2005-08-12T02:25:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0db1d6fc1ea051af49ebe03c503d23996a7c5bbb'/>
<id>urn:sha1:0db1d6fc1ea051af49ebe03c503d23996a7c5bbb</id>
<content type='text'>
Add limited retry logic to netpoll_send_skb

Each time we attempt to send, decrement our per-device retry counter.
On every successful send, we reset the counter. 

We delay 50us between attempts with up to 20000 retries for a total of
1 second. After we've exhausted our retries, subsequent failed
attempts will try only once until reset by success.

Signed-off-by: Matt Mackall &lt;mpm@selenic.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[NETPOLL]: allow multiple netpoll_clients to register against one interface</title>
<updated>2005-06-23T05:05:59Z</updated>
<author>
<name>Jeff Moyer</name>
</author>
<published>2005-06-23T05:05:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fbeec2e1552949002065435c9829dc244ad85407'/>
<id>urn:sha1:fbeec2e1552949002065435c9829dc244ad85407</id>
<content type='text'>
This patch provides support for registering multiple netpoll clients to the
same network device.  Only one of these clients may register an rx_hook,
however.  In practice, this restriction has not been problematic.  It is
worth mentioning, though, that the current design can be easily extended to
allow for the registration of multiple rx_hooks.

The basic idea of the patch is that the rx_np pointer in the netpoll_info
structure points to the struct netpoll that has rx_hook filled in.  Aside
from this one case, there is no need for a pointer from the struct
net_device to an individual struct netpoll.

A lock is introduced to protect the setting and clearing of the np_rx
pointer.  The pointer will only be cleared upon netpoll client module
removal, and the lock should be uncontested.

Signed-off-by: Jeff Moyer &lt;jmoyer@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[NETPOLL]: Introduce a netpoll_info struct</title>
<updated>2005-06-23T05:05:31Z</updated>
<author>
<name>Jeff Moyer</name>
</author>
<published>2005-06-23T05:05:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=115c1d6e61b70851d9a363328c3b8d4c2559a1d3'/>
<id>urn:sha1:115c1d6e61b70851d9a363328c3b8d4c2559a1d3</id>
<content type='text'>
This patch introduces a netpoll_info structure, which the struct net_device
will now point to instead of pointing to a struct netpoll.  The reason for
this is two-fold: 1) fields such as the rx_flags, poll_owner, and poll_lock
should be maintained per net_device, not per netpoll;  and 2) this is a first
step in providing support for multiple netpoll clients to register against the
same net_device.

The struct netpoll is now pointed to by the netpoll_info structure.  As
such, the previous behaviour of the code is preserved.

Signed-off-by: Jeff Moyer &lt;jmoyer@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[NETPOLL]: Set poll_owner to -1 before unlocking in netpoll_poll_unlock()</title>
<updated>2005-06-23T05:04:55Z</updated>
<author>
<name>Jeff Moyer</name>
</author>
<published>2005-06-23T05:04:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6ca4f65e6b390d09e1de7280cf9fd4f5d8e4b48b'/>
<id>urn:sha1:6ca4f65e6b390d09e1de7280cf9fd4f5d8e4b48b</id>
<content type='text'>
This trivial patch moves the assignment of poll_owner to -1 inside of
the lock.  This fixes a potential SMP race in the code.

Signed-off-by: Jeff Moyer &lt;jmoyer@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2'/>
<id>urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2</id>
<content type='text'>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!
</content>
</entry>
</feed>
