Begin forwarded message:
Date: Thu, 09 Feb 2006 06:10:49 +0100
From: Knut Petersen <[EMAIL PROTECTED]>
To: linux-kernel@vger.kernel.org
Subject: Assert: CPU #..., mangle/filter comefrom() = ...
As there probably is a reason to printk assertions:
[ 28.616455] ADDRCONF(NETDEV_CHANGE): eth
On 2/8/06, David S. Miller <[EMAIL PROTECTED]> wrote:
> From: Jesse Brandeburg <[EMAIL PROTECTED]>
> Date: Wed, 8 Feb 2006 12:07:14 -0800
>
> > this should be on netdev (cc'd), i included some of the thread here.
> ...
> > I though Herbert had fixed these, and it looks like half the patches
> > go
David S. Miller <[EMAIL PROTECTED]> wrote:
> From: Nicolas DICHTEL <[EMAIL PROTECTED]>
> Date: Mon, 06 Feb 2006 12:00:30 +0100
>
>> in the same way of this patch, why dst_entry are stored for
>> RAW socket ? In case of specific IPSec rules for ICMPv6,
>> xfrm state can be different for the same de
On Tue, 7 Feb 2006, Herbert Xu wrote:
I share your feelings towards this patch. However, what e1000 is doing
is broken. It should be filling in the frags array, not frag_list.
Okay, this implies all of our data will be in pages. Does this mean that
we have to copy the header back to skb->d
On Thu, 2006-09-02 at 03:40 +0300, Alexey Kuznetsov wrote:
> Hello!
>
> > BTW, Alexey - if you have a chance can you look at the breakage of
> > sendmsg() in relation to multicast that exists today?
>
> If it is is about groups > 31, which cannot be mapped to nl_groups,
> it is possible just to a
On Mon, Jan 30, 2006 at 02:28:43PM -0800, Jean Tourrilhes wrote:
> On Mon, Jan 30, 2006 at 01:28:44PM -0500, Dan Williams wrote:
> >
> > I'll post a revert patch for the patch I originally sent so that we go
> > back to the original behavior.
>
> Sorry, I may have overreacted. I think that'
From: jamal <[EMAIL PROTECTED]>
Date: Wed, 08 Feb 2006 19:07:25 -0500
> On Thu, 2006-09-02 at 01:46 +0300, Alexey Kuznetsov wrote:
> > Hello!
> >
> > > What about the dilemma of when there are no netlink sockets
> > > involved? ;->
> > > i.e what is the semantics when there is no netlink socket
Hello!
> BTW, Alexey - if you have a chance can you look at the breakage of
> sendmsg() in relation to multicast that exists today?
If it is is about groups > 31, which cannot be mapped to nl_groups,
it is possible just to add setsockopt(), setting dst_group. It is just
to complete the API.
Do s
From: Jesse Brandeburg <[EMAIL PROTECTED]>
Date: Wed, 8 Feb 2006 16:30:04 -0800 (Pacific Standard Time)
> Basically it appears that code has been there for a long time (since 2.4)
> and both e1000 and other drivers use it. If the change to
> skb_copy_datagram_iovec is reverted, this method of c
On Tue, 7 Feb 2006, David S. Miller wrote:
From: Jesse Brandeburg <[EMAIL PROTECTED]>
Date: Tue, 7 Feb 2006 17:41:28 -0800 (Pacific Standard Time)
> so we generally call dev_alloc_skb to get the receive buffers to give to
> our hardware. When we use multiple receive buffers what is the right wa
On Thu, 2006-09-02 at 01:46 +0300, Alexey Kuznetsov wrote:
> Hello!
>
> > What about the dilemma of when there are no netlink sockets
> > involved? ;->
> > i.e what is the semantics when there is no netlink socket to map them
> > to, such as in the case of ioctl?
>
> 0, which is legal address of
On Wed, Feb 08, 2006 at 03:58:59PM -0800, David S. Miller wrote:
> From: Herbert Xu <[EMAIL PROTECTED]>
> Date: Thu, 09 Feb 2006 10:49:37 +1100
>
> > The difference between gcc -pedantic and sparse is that it doesn't
> > warn about obviously correct cases like p != 0 or p = 0.
>
> So obviously co
On Wed, 8 Feb 2006, David S. Miller wrote:
> From: Herbert Xu <[EMAIL PROTECTED]>
> Date: Thu, 09 Feb 2006 10:49:37 +1100
>
> > The difference between gcc -pedantic and sparse is that it doesn't
> > warn about obviously correct cases like p != 0 or p = 0.
>
> So obviously correct that you left out
In article <[EMAIL PROTECTED]> (at Wed, 08 Feb 2006 15:59:31 -0800 (PST)),
"David S. Miller" <[EMAIL PROTECTED]> says:
> > Good spot. Please drop {}, otherwise, I agree. Thank you.
>
> I'll take care of fixing that when I put in the fix.
Okay, thanks.
Acked-by: YOSHIFUJI Hideaki <[EMAIL PROT
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Thu, 09 Feb 2006 10:49:37 +1100
> The difference between gcc -pedantic and sparse is that it doesn't
> warn about obviously correct cases like p != 0 or p = 0.
So obviously correct that you left out an equals sign in the
second case :-)
-
To unsubscribe
From: YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
Date: Thu, 09 Feb 2006 08:44:36 +0900 (JST)
> Hello.
>
> In article <[EMAIL PROTECTED]> (at Wed, 08 Feb 2006 17:17:24 +0200), Kristian
> Slavov <[EMAIL PROTECTED]> says:
>
> > During NETDEV_DOWN we clear IF_READY, and we don't set it back in
> > NETD
Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
>
> Oh, and for the record: current sparse from Linus doesn't warn about
> this. Slightly modified sparse warns. Bugs which were uncovered by
> more or less trivial and slightly broken sparse patch [1] are:
>
>[PATCH] dscc4: fix dscc4_init_dummy_
Hello.
In article <[EMAIL PROTECTED]> (at Wed, 08 Feb 2006 17:17:24 +0200), Kristian
Slavov <[EMAIL PROTECTED]> says:
> During NETDEV_DOWN we clear IF_READY, and we don't set it back in
> NETDEV_UP. While starting to perform DAD on the link-local address, we
> notice that the device is not in
Alexey Dobriyan writes:
> The fact that they can be represented by the same bit patterns is
> irrelevant.
Indeed it is. The fact that the C standard says that "0" is a valid
representation for a null pointer in C source code *is* relevant,
though. That is in fact something that *wasn't* in K&R
On Thursday 09 February 2006 00:07, David Stevens wrote:
> From: Stephen Hemminger <[EMAIL PROTECTED]>
>
> > IMHO converting skb->dev to skb->devindex and using ifindex sounds best.
> > It gets rid of the need to refcount as much but keeps the safety from
> > buggy protocols. Ipv6 could probably
On Wed, Feb 08, 2006 at 02:47:12PM -0800, David S. Miller wrote:
> From: David Stevens <[EMAIL PROTECTED]>
> Date: Wed, 8 Feb 2006 14:45:08 -0800
>
> > Why would sparse complain about this? 0 is a well-defined
> > pointer value (the only value guaranteed to be by the language).
>
> Becaus
jamal wrote:
> a) if user-app using netlink modifies something, the event will report
> the nl_pid mapped to its pid or other non-zero value depending on
> the number of netlink sockets mapped to that process/user-app
It will always be nl_pid of the socket. And don't forget that this pid and
nega
From: Stephen Hemminger <[EMAIL PROTECTED]>
> IMHO converting skb->dev to skb->devindex and using ifindex sounds best.
> It gets rid of the need to refcount as much but keeps the safety from
> buggy protocols. Ipv6 could probably use ifindex as well.
A couple years ago, we identified a p
On Wed, Feb 08, 2006 at 02:45:08PM -0800, David Stevens wrote:
> [EMAIL PROTECTED] wrote on 02/08/2006 02:19:20 PM:
>
> > James Carlson <[EMAIL PROTECTED]> wrote:
> > > Alexey Dobriyan writes:
> > >> - if (ap == 0)
> > >> + if (!ap)
> > >
> > > And the solution is to treat it as a boolean
David S. Miller wrote:
From: David Stevens <[EMAIL PROTECTED]>
Date: Wed, 8 Feb 2006 14:45:08 -0800
Why would sparse complain about this? 0 is a well-defined
pointer value (the only value guaranteed to be by the language).
Because sparse goes beyond the standards and tries to
catch c
David S. Miller writes:
> Because sparse goes beyond the standards and tries to
> catch cases that usually end up being bugs.
When has a pointer comparison with an explicit "0" ever caused a bug?
Paul.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message t
Hello!
> What about the dilemma of when there are no netlink sockets
> involved? ;->
> i.e what is the semantics when there is no netlink socket to map them
> to, such as in the case of ioctl?
0, which is legal address of kernel socket.
In this case it means that "kernel" did the operation.
Mor
From: David Stevens <[EMAIL PROTECTED]>
Date: Wed, 8 Feb 2006 14:45:08 -0800
> Why would sparse complain about this? 0 is a well-defined
> pointer value (the only value guaranteed to be by the language).
Because sparse goes beyond the standards and tries to
catch cases that usually end up
James Carlson writes:
> Alexey Dobriyan writes:
> > - if (ap == 0)
> > + if (!ap)
>
> And the solution is to treat it as a boolean instead?! I'm not sure
> which is more ugly.
>
> Why wouldn't explicit comparison against NULL be the preferred fix?
I just think this whole "you shouldn't com
From: Andi Kleen <[EMAIL PROTECTED]>
Date: Wed, 8 Feb 2006 23:20:38 +0100
> But are you sure the hash table used for that would be strong enough
> to handle the load?
With RCU locking I think it is.
> And what happens when a ifindex is reused? Then packets could end up
> on the wrong interface.
[EMAIL PROTECTED] wrote on 02/08/2006 02:19:20 PM:
> James Carlson <[EMAIL PROTECTED]> wrote:
> > Alexey Dobriyan writes:
> >> - if (ap == 0)
> >> + if (!ap)
> >
> > And the solution is to treat it as a boolean instead?! I'm not sure
> > which is more ugly.
>
> Treating it as a boolean
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Wed, 8 Feb 2006 13:08:41 -0800
> If you want to find a patch that made things better/worse
> (and it is post git). Look into "git bisect"
He's referencing bkbits URLs, I don't think he even knows
what GIT is :-)
-
To unsubscribe from this list: s
The ethernet controller is integrated into the chipset. Therefore, no
mismatch between MSI/MSIX chipset support and device support should exist.
Ayaz
Roland Dreier wrote:
Roland> Is forcedeth ever used with a discrete ethernet
Roland> controller? I thought that nforce NICs are always
James> And the solution is to treat it as a boolean instead?! I'm
James> not sure which is more ugly.
James> Why wouldn't explicit comparison against NULL be the
James> preferred fix?
"if (ptr)" and "if (!ptr)" are the preferred idiom for testing whether
a pointer is NULL. What
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Wed, 08 Feb 2006 13:02:15 -0500
> Ravinandan Arakali wrote:
> > Hi,
> > Just wondering if anybody got a chance to review the below patch.
> > This version(as per Rick's comment on v1 patch) includes support
> > for TCP timestamps.
>
> It's been merged i
James Carlson <[EMAIL PROTECTED]> wrote:
> Alexey Dobriyan writes:
>> - if (ap == 0)
>> + if (!ap)
>
> And the solution is to treat it as a boolean instead?! I'm not sure
> which is more ugly.
Treating it as a boolean looks good to me. It's better than the existing
code because it shuts
On Wednesday 08 February 2006 20:12, Stephen Hemminger wrote:
> On Tue, 07 Feb 2006 16:26:01 -0800 (PST)
> "David S. Miller" <[EMAIL PROTECTED]> wrote:
>
> > From: Stephen Hemminger <[EMAIL PROTECTED]>
> > Date: Tue, 7 Feb 2006 16:19:42 -0800
> >
> > > Also, isn't a lot of the problem reduced if
From: Eric Dumazet <[EMAIL PROTECTED]>
Date: Wed, 08 Feb 2006 16:06:31 +0100
> loopback driver carefully uses per_cpu storage for statistics but updates
> loopback_dev.last_rx
This has been discussed before, this is an attribute every
driver must keep uptodate. Things like bonding use it,
for e
jamal wrote:
> So the question is what would be the "address"/nl_pid of something
> issued by an ioctl (refer to my earlier email to Alexey).
It's the kernel who creates this message and puts it to the netlink
domain, so I'd say 0.
--
Hasso Tepper
-
To unsubscribe from this list: send the line
From: Nicolas DICHTEL <[EMAIL PROTECTED]>
Date: Mon, 06 Feb 2006 12:00:30 +0100
> in the same way of this patch, why dst_entry are stored for
> RAW socket ? In case of specific IPSec rules for ICMPv6,
> xfrm state can be different for the same destination.
> Attached, a proposed patch.
We cache t
From: Jesse Brandeburg <[EMAIL PROTECTED]>
Date: Wed, 8 Feb 2006 12:07:14 -0800
> this should be on netdev (cc'd), i included some of the thread here.
...
> I though Herbert had fixed these, and it looks like half the patches
> got into 2.6.14.3, but not the fix to the fix committed on 9-6 (not i
Alexey Dobriyan writes:
> - if (ap == 0)
> + if (!ap)
And the solution is to treat it as a boolean instead?! I'm not sure
which is more ugly.
Why wouldn't explicit comparison against NULL be the preferred fix?
--
James Carlson 42.703N 71.076W <[EMAIL PROTECTED]>
-
To un
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
ppp is the biggest offender.
drivers/net/ppp_async.c | 34 ++--
drivers/net/ppp_generic.c | 128 +++---
drivers/net/ppp_synctty.c | 26 -
drivers/net/pppoe.c |2
4 fil
On Wed, 2006-08-02 at 23:41 +0200, Hasso Tepper wrote:
> jamal wrote:
> > At the moment if a route (v6 or v4) was added by quagga and i had a
> > socket that was listening in a different process - what pid will i see
> > (in my user space app)? Is it of the quagga process or is it 0?
>
> No, it's
jamal wrote:
> On Wed, 2006-08-02 at 22:50 +0200, Hasso Tepper wrote:
> > jamal wrote:
> > > Ok, thanks for the reminder Hasso.
> > > so essentially at the moment the pid that will show up (if
> > > quagga added the v6 route) will be that of quagga, correct?
> >
> > No. Quote from Alexey:
>
> I sen
On Thu, 2006-09-02 at 00:02 +0300, Alexey Kuznetsov wrote:
> I am afraid It is not logical and inconsistent and really breaks
> netlink. :-)
>
> Those nl_pid's are _addresses_ of netlink sockets. You cannot fill them
> with random numbers.
>
Ok, Alexey:
What about the dilemma of when there are
On Wed, 08 Feb 2006 12:18:23 -0800
David Carlton <[EMAIL PROTECTED]> wrote:
> On Mon, 06 Feb 2006 15:50:28 -0800 (PST), "David S. Miller" <[EMAIL
> PROTECTED]> said:
>
> > From: David Carlton <[EMAIL PROTECTED]>
> > Date: Mon, 06 Feb 2006 14:38:10 -0800
>
> >> I'm working on an application that
On Wed, 2006-08-02 at 22:50 +0200, Hasso Tepper wrote:
> jamal wrote:
> > Ok, thanks for the reminder Hasso.
> > so essentially at the moment the pid that will show up (if
> > quagga added the v6 route) will be that of quagga, correct?
>
> No. Quote from Alexey:
>
I sense you missed my question.
Hello!
> Ok, thanks for the reminder Hasso.
> so essentially at the moment the pid that will show up (if
> quagga added the v6 route) will be that of quagga, correct?
In the part, where v6 routes added via netlink it was a long expected
thing.. I was lazy in many places to pass identity of author
On Wed, 08 Feb 2006 12:20:22 -0800
Ben Greear <[EMAIL PROTECTED]> wrote:
> I have a dual-port SysKonnect NIC. In 'lspci' I see one entry
> (was expecting two..but maybe that is a separate issue). The
> chipset appears to be SK-9Exx 10/100/1000Base-T adapter (rev 12).
>
> skge does not seem to s
jamal wrote:
> Ok, thanks for the reminder Hasso.
> so essentially at the moment the pid that will show up (if
> quagga added the v6 route) will be that of quagga, correct?
No. Quote from Alexey:
"Netlink "pid" has nothing to do with current->pid. I called it
incorrectly, if it was named "port",
Ok, thanks for the reminder Hasso.
so essentially at the moment the pid that will show up (if
quagga added the v6 route) will be that of quagga, correct?
Same with v4 iirc? If yes, then isnt it logical that if ifconfig added
an ip address it should naturally be ifconfig's pid that shows up (for
co
I have a dual-port SysKonnect NIC. In 'lspci' I see one entry
(was expecting two..but maybe that is a separate issue). The
chipset appears to be SK-9Exx 10/100/1000Base-T adapter (rev 12).
skge does not seem to support this NIC (in 2.6.15). Is there
another driver that does?
Thanks,
Ben
--
B
On Mon, 06 Feb 2006 15:50:28 -0800 (PST), "David S. Miller" <[EMAIL PROTECTED]>
said:
> From: David Carlton <[EMAIL PROTECTED]>
> Date: Mon, 06 Feb 2006 14:38:10 -0800
>> I'm working on an application that we're trying to switch from a 2.4
>> kernel to a 2.6 kernel. (I believe we're using 2.6.9
Stephen Hemminger wrote:
On Wed, 08 Feb 2006 11:24:24 -0800
Ben Greear <[EMAIL PROTECTED]> wrote:
Stephen Hemminger wrote:
On Tue, 07 Feb 2006 16:26:01 -0800 (PST)
"David S. Miller" <[EMAIL PROTECTED]> wrote:
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Tue, 7 Feb 2006 16:19:42 -080
On 2/8/06, Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> On Wed, 08 Feb 2006 11:24:24 -0800
> Ben Greear <[EMAIL PROTECTED]> wrote:
>
> > Stephen Hemminger wrote:
> > > On Tue, 07 Feb 2006 16:26:01 -0800 (PST)
> > > "David S. Miller" <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >>From: Stephen Hemmi
Hasso Tepper wrote:
> No, that was different issue and isn't related with issue Alexey
> poiting to. The issue I complained and you fixed it, Jamal, was that
> IPv6 related netlink messages had always pid 0 even if they were issued
> by application.
It was unclear, so I have to correct myself - ".
this should be on netdev (cc'd), i included some of the thread here.
On 2/7/06, Yoseph Basri <[EMAIL PROTECTED]> wrote:
> Hello kernel maillist,
>
> I'm new member maillist.
>
> Currently, I receive the warning log from my kernel.
>
> Since update to
> Linux 2.6.14.3 #1 SMP Fri Nov 25 20:20:05 SG
On Wed, 08 Feb 2006 11:24:24 -0800
Ben Greear <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger wrote:
> > On Tue, 07 Feb 2006 16:26:01 -0800 (PST)
> > "David S. Miller" <[EMAIL PROTECTED]> wrote:
> >
> >
> >>From: Stephen Hemminger <[EMAIL PROTECTED]>
> >>Date: Tue, 7 Feb 2006 16:19:42 -0800
> >>
Stephen Hemminger wrote:
On Tue, 07 Feb 2006 16:26:01 -0800 (PST)
"David S. Miller" <[EMAIL PROTECTED]> wrote:
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Tue, 7 Feb 2006 16:19:42 -0800
Also, isn't a lot of the problem reduced if network devices
are affinitied?
Not for routing/firew
On Wed, Feb 08, 2006 at 05:17:24PM +0200, Kristian Slavov wrote:
> During NETDEV_DOWN we clear IF_READY, and we don't set it back in
> NETDEV_UP. While starting to perform DAD on the link-local address, we
> notice that the device is not in IF_READY, and we abort autoconfiguration
> process (whi
On Tue, 07 Feb 2006 16:26:01 -0800 (PST)
"David S. Miller" <[EMAIL PROTECTED]> wrote:
> From: Stephen Hemminger <[EMAIL PROTECTED]>
> Date: Tue, 7 Feb 2006 16:19:42 -0800
>
> > Also, isn't a lot of the problem reduced if network devices
> > are affinitied?
>
> Not for routing/firewalling, we tou
Ravinandan Arakali wrote:
Hi,
Just wondering if anybody got a chance to review the below patch.
This version(as per Rick's comment on v1 patch) includes support
for TCP timestamps.
It's been merged in the 'lro' branch of netdev-2.6.git for a little
while now. Once it gets additional review (a
jamal wrote:
> On Wed, 2006-08-02 at 18:27 +0300, Alexey Kuznetsov wrote:
> > When a netlink message is not related to a netlink socket,
> > it is issued by kernel socket with pid 0. Netlink "pid" has nothing
> > to do with current->pid. I called it incorrectly, if it was named
> > "port", the conf
Hi,
Just wondering if anybody got a chance to review the below patch.
This version(as per Rick's comment on v1 patch) includes support
for TCP timestamps.
Thanks,
Ravi
-Original Message-
From: Ravinandan Arakali [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 25, 2006 11:53 AM
To: [EMA
Hi Alexey,
On Wed, 2006-08-02 at 18:27 +0300, Alexey Kuznetsov wrote:
> Hello!
>
> When a netlink message is not related to a netlink socket,
> it is issued by kernel socket with pid 0. Netlink "pid" has nothing
> to do with current->pid. I called it incorrectly, if it was named "port",
> the con
Hello!
When a netlink message is not related to a netlink socket,
it is issued by kernel socket with pid 0. Netlink "pid" has nothing
to do with current->pid. I called it incorrectly, if it was named "port",
the confusion would be avoided.
Jamal, please, review. Did you have reasons to do this?
Hi,
If you set network interface down and up again, the IPv6 address
autoconfiguration does not work. 'ip addr' shows that the link-local
address is in tentative state. We don't even react to periodical router
advertisements.
During NETDEV_DOWN we clear IF_READY, and we don't set it back in
loopback driver carefully uses per_cpu storage for statistics but updates
loopback_dev.last_rx
As last_rx is only used by bond driver to detect link activity, and loopback
dev wont be used as a bond slave, can we avoid this write access that slowdown
SMP platforms, because of cache ping pongs
Hello!
netlink overrun was broken while improvement of netlink.
Destination socket is used in the place where it was meant to be source socket,
so that now overrun is never sent to user netlink sockets, when it should be,
and it even can be set on kernel socket, which results in complete deadlock
On 2/8/06, Roberto Nibali <[EMAIL PROTECTED]> wrote:
> I've thought about the linux/modules.h header (ignoring the fact
> mentioned by Herbert because of its small chance of happening) and my
> suggestion was/is to move it to ip_vs.h. I'll ping Arnaldo regarding
> this cleanup, since he's done it
Hi,
On Sat, Feb 04, 2006 at 01:31:16PM +0200, Denis Vlasenko wrote:
> On Friday 03 February 2006 12:58, Andreas Mohr wrote:
> > - use "% 8" modulo instead of more complicated "% 5" calculation
>
> Why? There will be HZ=100 and HZ=250 boxes, 8ms doesn't fit well.
> 10ms is ok, 5ms or 2.5ms is more
From: Dale Farnsworth <[EMAIL PROTECTED]>
Signed-off-by: Dale Farnsworth <[EMAIL PROTECTED]>
---
These includes were added twice:
in commit 78a5e534758349fd3effc90ce1152b55368f52ee by Olaf Hering and
in commit b6298c22c5e9f698812e2520003ee178aad50c10 by Al Viro.
This patch reverts 78a5e534758349
Hi folks,
If someone has cardbus acx, please test this one.
Basically, in acxpci_e_remove() we will check the presence
of the card by reading a register and if it is not all ones,
we will command device to shut down.
Previously it was done in acxpci_e_cleanup_module().
+INLINE_IO int
+adev_pres
On Wed, Feb 08, 2006 at 07:46:48AM +1100, Herbert Xu wrote:
> I suggest that we simply bail out always. If the dst decides to die
> on us later on, the packet will be dropped anyway. So there is no
> great urgency to retry here. Once we have the proper resolution
> queueing, we can then do the r
On Wednesday 08 February 2006 11:34, Eric Dumazet wrote:
> 1) Instead of storing a 2-uple {pointer,generation} (and using 12 or 16 bytes
> on 64 bits platforms), we could just use a 32 bit quantity
> [(ifindex<<8)+(gen_number)]
That would add an 2^24 netdevice limit. Someone will sooner or late
Andi Kleen a écrit :
On Wednesday 08 February 2006 01:44, David S. Miller wrote:
From: Ben Greear <[EMAIL PROTECTED]>
Date: Tue, 07 Feb 2006 16:39:52 -0800
Rick Jones wrote:
In the realm of straw ideas, how often are netdevs added and removed,
and would leaving a tombstone behind consume too
On Wed, Feb 08, 2006 at 02:26:32PM +0900, FUJITA Tomonori ([EMAIL PROTECTED])
wrote:
> Mike Christie and I've developed the SCSI Userspace target
> framework. Target LLDs (for Fibre channel, iSCSI HBAs, etc) pass SCSI
> commands to SCSI commands to the user-space daemon. The daemon
> executes the
On Tuesday 07 February 2006 22:04, Carlos Martín wrote:
> Content-Transfer-Encoding: quoted-printable
Patch was damaged. I think sending them as plain-text attachment
would work better.
> Add _{get,set}_encodeext and improve logging in _encode
>
> The code in _{get,set}_encode has be
> [PATCH] Better fixup for the orinoco driver
>
> The latest kernel added a pretty ugly fix for the orinoco etherleak bug
> which contains bogus skb->len checks already done by the caller and causes
> copies of all odd sized frames (which are quite common)
>
> While the skb->len check should be r
On Wednesday 08 February 2006 01:44, David S. Miller wrote:
> From: Ben Greear <[EMAIL PROTECTED]>
> Date: Tue, 07 Feb 2006 16:39:52 -0800
>
> > Rick Jones wrote:
> > > In the realm of straw ideas, how often are netdevs added and removed,
> > > and would leaving a tombstone behind consume too muc
On Tue, Feb 07, 2006 at 09:07:34PM -0800, David S. Miller wrote:
> From: Horms <[EMAIL PROTECTED]>
> Date: Wed, 8 Feb 2006 12:09:29 +0900
>
> > Unfortunately this seems like it is going to be more tedious than
> > we first thought. I would guess writing some sort of tool to analyse
> > symbols an
The correct way to go about this is to go through each included header
file and check if any of its symbols are used in the source file.
Or if this is too tedious just leave it alone.
Hi Herbert,
thanks for your feedback.
Dave,
please discard this patch for now.
Ratz,
Unfortunately thi
83 matches
Mail list logo
