From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: small patch - 2.4.21-pre7 net/core/bk
Date: 21 Apr 2003 19:57:57 +0100 [thread overview]
Message-ID: <1050951477.1859.14.camel@flat41> (raw)
In-Reply-To: <1050950810.2738.10.camel@flat41>
On Mon, 2003-04-21 at 19:46, Grzegorz Jaskiewicz wrote:
> Maybe i just don't understeand this part of code, but i think we
should
> not give calling driver five chances :)
>
of course it should be:
-----------------------------------------------------------------
--- net/core/skbuff.c.org 2003-04-21 19:42:35.000000000 +0100
+++ net/core/skbuff.c 2003-04-21 19:43:10.000000000 +0100
@@ -167,13 +167,9 @@
u8 *data;
if (in_interrupt() && (gfp_mask & __GFP_WAIT)) {
- static int count = 0;
- if (++count < 5) {
- printk(KERN_ERR "alloc_skb called nonatomically
"
- "from interrupt %p\n", NET_CALLER(size));
- BUG();
- }
- gfp_mask &= ~__GFP_WAIT;
+ printk(KERN_ERR "alloc_skb called nonatomically "
+ "from interrupt %p\n", NET_CALLER(size));
+ BUG();
}
/* Get the HEAD */
-----------------------------------------------------------------
> Also, i am bit confused with this part :
> /* Get the DATA. Size must match skb_add_mtu(). */
> size = SKB_DATA_ALIGN(size);
> data = kmalloc(size + sizeof(struct skb_shared_info),
gfp_mask);
> if (data == NULL)
> goto nodata;
>
> /* XXX: does not include slab overhead */
> skb->truesize = size + sizeof(struct sk_buff);
>
> can anybody explain me please why skb->truesize gets
size+sizeof(struct
> sk_buff) (acording to XXX above it, it is incorrect).
--
Grzegorz Jaskiewicz aka Kain/K4
K4 labs
prev parent reply other threads:[~2003-04-21 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 18:46 small patch - 2.4.21-pre7 net/core/bk Grzegorz Jaskiewicz
2003-04-21 18:57 ` Grzegorz Jaskiewicz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1050951477.1859.14.camel@flat41 \
--to=gj@pointblue.com.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.