From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [Q] LL_RESERVED_SPACE(dev) vs HH_DATA_ALIGN(dev->hard_header_len)
Date: Sun, 8 Feb 2004 13:03:04 -0800 [thread overview]
Message-ID: <20040208130304.5df8e2c3.davem@redhat.com> (raw)
In-Reply-To: <20040208.203930.36073978.yoshfuji@linux-ipv6.org>
On Sun, 08 Feb 2004 20:39:30 +0900 (JST)
YOSHIFUJI Hideaki / ^[$B5HF#1QL@^[(B <yoshfuji@linux-ipv6.org> wrote:
> Question:
> How do you think about the following patch?
> Or, is it okay to simply use LL_RESERVED_SPACE(dev) in both places?
LL_RESERVED_SPACE() is what should be used in both spots.
I checked in the following patch, thanks for noticing this.
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/02/08 12:58:29-08:00 davem@nuts.davemloft.net
# [ECONET]: Use LL_RESERVED_SPACE() where applicable. Noticed by yoshfuji.
#
# net/econet/af_econet.c
# 2004/02/08 12:58:13-08:00 davem@nuts.davemloft.net +2 -2
# [ECONET]: Use LL_RESERVED_SPACE() where applicable. Noticed by yoshfuji.
#
diff -Nru a/net/econet/af_econet.c b/net/econet/af_econet.c
--- a/net/econet/af_econet.c Sun Feb 8 12:59:08 2004
+++ b/net/econet/af_econet.c Sun Feb 8 12:59:08 2004
@@ -318,12 +318,12 @@
#ifdef CONFIG_ECONET_NATIVE
dev_hold(dev);
- skb = sock_alloc_send_skb(sk, len+dev->hard_header_len+15,
+ skb = sock_alloc_send_skb(sk, len+LL_RESERVED_SPACE(dev),
msg->msg_flags & MSG_DONTWAIT, &err);
if (skb==NULL)
goto out_unlock;
- skb_reserve(skb, (dev->hard_header_len+15)&~15);
+ skb_reserve(skb, LL_RESERVED_SPACE(dev));
skb->nh.raw = skb->data;
eb = (struct ec_cb *)&skb->cb;
prev parent reply other threads:[~2004-02-08 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 11:39 [Q] LL_RESERVED_SPACE(dev) vs HH_DATA_ALIGN(dev->hard_header_len) YOSHIFUJI Hideaki / 吉藤英明
2004-02-08 21:03 ` David S. Miller [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=20040208130304.5df8e2c3.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).