From: David Miller <davem@davemloft.net>
To: peterchacko35@gmail.com
Cc: rick.jones2@hp.com, radhamohan_ch@yahoo.com, netdev@vger.kernel.org
Subject: Re: can we reuse an skb
Date: Sat, 20 Jun 2009 22:49:12 -0700 (PDT) [thread overview]
Message-ID: <20090620.224912.217086631.davem@davemloft.net> (raw)
In-Reply-To: <1f808b4a0906202241l1d74364ft52d99ecb6b0274f5@mail.gmail.com>
From: Peter Chacko <peterchacko35@gmail.com>
Date: Sun, 21 Jun 2009 11:11:16 +0530
> Here i am considering a special case where Linux stack is not used in
> a host environment. Its dedicated packet processor. Application data
> is not expected. (discarded if thats the case).
Linux is a general purpose operating system.
You can modify it for your own needs, locally, however you want. But
upstream, we have to consider all use cases, not just your's.
next prev parent reply other threads:[~2009-06-21 5:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 6:46 can we reuse an skb Radha Mohan
2009-06-19 6:51 ` jon_zhou
2009-06-19 7:10 ` Radha Mohan
2009-06-19 7:21 ` Peter Chacko
2009-06-19 10:37 ` Saikiran Madugula
2009-06-19 18:41 ` Neil Horman
2009-06-19 16:56 ` Rick Jones
2009-06-19 23:29 ` David Miller
2009-06-20 3:54 ` Peter Chacko
2009-06-20 8:00 ` Evgeniy Polyakov
2009-06-20 11:51 ` Ben Hutchings
2009-06-21 5:41 ` Peter Chacko
2009-06-21 5:49 ` David Miller [this message]
2009-06-21 11:46 ` [RFD] Pluggable code design (was: can we reuse an skb) Al Boldi
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 10:11 can we reuse an skb Nicholas Van Orton
2009-06-22 13:34 ` Philby John
2009-06-22 13:56 ` Peter Chacko
2009-06-22 14:33 ` Philby John
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=20090620.224912.217086631.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=peterchacko35@gmail.com \
--cc=radhamohan_ch@yahoo.com \
--cc=rick.jones2@hp.com \
/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).