From: David Miller <davem@davemloft.net>
To: rapier@psc.edu
Cc: netdev@vger.kernel.org
Subject: Re: size of data_segs_[in|out] and segs_[in|out]
Date: Mon, 08 Aug 2016 16:02:45 -0700 (PDT) [thread overview]
Message-ID: <20160808.160245.2063863440275871547.davem@davemloft.net> (raw)
In-Reply-To: <797392fa-8d87-f45b-69b2-fdd096e1229c@psc.edu>
From: rapier <rapier@psc.edu>
Date: Mon, 8 Aug 2016 18:02:29 -0400
> As such, would it be feasible to define these instruments as 64bit
> instead of 32bit? If so, a cursory look at the code seems to indicate
> that this would only require a change in the header files.
It would break every application looking at these datastructures
right now.
next prev parent reply other threads:[~2016-08-08 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 22:02 size of data_segs_[in|out] and segs_[in|out] rapier
2016-08-08 23:02 ` David Miller [this message]
2016-08-09 17:17 ` rapier
2016-08-09 19:04 ` David Miller
2016-08-09 19:15 ` rapier
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=20160808.160245.2063863440275871547.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rapier@psc.edu \
/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).