From: kuznet@ms2.inr.ac.ru
To: andrea@suse.DE (Andrea Arcangeli)
Cc: davem@redhat.com (Dave Miller),
alan@lxorguk.ukuu.org.uk (Alan Cox),
linux-kernel@vger.kernel.org
Subject: Re: alloc_skb cannot be called with GFP_DMA
Date: Sun, 5 Aug 2001 21:18:11 +0400 (MSK DST) [thread overview]
Message-ID: <200108051718.VAA17521@ms2.inr.ac.ru> (raw)
In-Reply-To: <20010805181606.F21840@athlon.random> from "Andrea Arcangeli" at Aug 5, 1 08:45:01 pm
Hello!
> alloc_isa_skb will avoid to slowdown alloc_skb so I prefer it compared
> to hiding the logic inside alloc_skb.
Stop! This is redundant. GFP_DMA is for skb data, not head!
So that, it is enough and right to clear GFP_DMA inside
alloc_skb when allocating skb head.
Alexey
next prev parent reply other threads:[~2001-08-05 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 15:53 alloc_skb cannot be called with GFP_DMA Andrea Arcangeli
2001-08-05 16:03 ` Alan Cox
2001-08-05 16:16 ` Andrea Arcangeli
2001-08-05 17:18 ` kuznet [this message]
2001-08-05 18:38 ` Andrea Arcangeli
2002-09-26 21:18 Manfred Spraul
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=200108051718.VAA17521@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.DE \
--cc=davem@redhat.com \
--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 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).