From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: block layer sg, bsg
Date: 5 Aug 2004 01:21:16 +0200
Date: Thu, 5 Aug 2004 01:21:16 +0200 [thread overview]
Message-ID: <20040804232116.GA30152@muc.de> (raw)
In-Reply-To: <20040804122254.3d52c2d4.davem@redhat.com>
On Wed, Aug 04, 2004 at 12:22:54PM -0700, David S. Miller wrote:
> On Wed, 4 Aug 2004 15:18:50 -0400
> Jeff Garzik <jgarzik@pobox.com> wrote:
>
> > On Wed, Aug 04, 2004 at 07:28:04PM +0200, Andi Kleen wrote:
> > > So please never pass any structures with read/write/netlink.
> >
> > Sorry... This is pretty much a given IMO.
>
> Yes, netlink would be a nop if we gave in to Andi's reccomendation
> :-)
Well, 32bit ipsec on x86-64/ia64 is a NOP because of that.
Alternatively for me it would be enough if you never use long long
in such data structures. That is what broke ipsec. And it's pretty
much unfixable because netlink is so adverse to emulation layers.
Longer term adding a presentation layer to netlink will be likely
a good idea. That's also needed for the cluster netlink stuff some
people are talking about.
-Andi
next prev parent reply other threads:[~2004-08-04 23:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ppN4-1wi-11@gated-at.bofh.it>
[not found] ` <2pvps-5xO-33@gated-at.bofh.it>
[not found] ` <2pvz2-5Lf-19@gated-at.bofh.it>
[not found] ` <2pwbQ-68b-43@gated-at.bofh.it>
2004-08-04 17:28 ` block layer sg, bsg Andi Kleen
2004-08-04 17:31 ` Jens Axboe
2004-08-04 19:18 ` Jeff Garzik
2004-08-04 19:22 ` David S. Miller
2004-08-04 23:21 ` Andi Kleen [this message]
2004-08-04 23:26 ` David S. Miller
2004-08-04 23:51 ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-05 3:58 ` David S. Miller
2004-08-06 7:03 ` Daniel Phillips
2004-08-06 15:04 ` Andi Kleen
2004-08-08 19:18 ` Daniel Phillips
2004-08-05 11:49 ` Andi Kleen
2004-08-06 3:46 ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-06 4:19 ` David S. Miller
2004-08-06 13:20 ` Andi Kleen
2004-08-06 18:28 ` David S. Miller
2004-08-06 11:04 ` Andi Kleen
2004-08-04 8:50 Jens Axboe
2004-08-04 14:52 ` David S. Miller
2004-08-04 15:04 ` Jens Axboe
2004-08-04 15:44 ` David S. Miller
2004-08-04 15:48 ` Jens Axboe
2004-08-04 15:56 ` Jeff Garzik
2004-08-04 15:58 ` Jens Axboe
2004-08-04 23:11 ` Douglas Gilbert
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=20040804232116.GA30152@muc.de \
--to=ak@muc.de \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.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