From: Matthias Fruehauf <mfrueh@suse.de>
To: Mehulkumar J Patel <mehul.patel@in.ibm.com>
Cc: Olaf Hering <olh@suse.de>, Anil K Prasad <aprasad@in.ibm.com>,
Kaena Freitas <kaena@us.ibm.com>,
olaf@suse.de, netdev@oss.sgi.com
Subject: Re: Linux kernel updates and ip_crossover patch
Date: Thu, 30 Oct 2003 14:16:29 +0100 [thread overview]
Message-ID: <20031030131628.GL17431@suse.de> (raw)
In-Reply-To: <OF5B9BCA99.0441857B-ON65256DCF.004761FF-65256DCF.004828A5@in.ibm.com>
On Thu, Oct 30, Mehulkumar J Patel wrote:
>
> Hello All,
>
> Any update on this.
>
> Basically we need IP CROSSOVER patch to be part of pseries kernel.
Well, I am not completly sure what we are talking about here ... ;-) The
usuall way if someone wants features to become part of the kernel is via
the community, in this case via the network guys as Olaf suggested or if
it is a plattform specific thing via the plattform maintainer, which is
David Engebretsen <engebret@us.ibm.com> for example for PPC at IBM.
In case that there is for some reason no solution going this path, IBM
has the possibility to request features from SuSE via the brands and via
the LTC. This is organized by Mark VanderWiele <markv@us.ibm.com>.
To be more specific: For 2.4 kernel the door is allready closed since
some weeks. In case you would like to see this patch in an upcoming SLES
9 and a 2.6 kernel, get in contact with Dave and Mark.
Hope this helps for the moment.
> best regards,
> Mehul.
>
Best regards,
Matthias Frühauf
>
> Olaf Hering
> <olh@suse.de> To: Kaena Freitas <kaena@us.ibm.com>, Mehulkumar
> J Patel/India/IBM@IBMIN
> 29/09/2003 cc: Mehulkumar J Patel/India/IBM@IBMIN, Matthias
> 16:40 Fruehauf <mfrueh@suse.de>, olaf@suse.de, Anil K Prasad/India/
> IBM@IBMIN, Daljeet Maini/India/IBM@IBMIN
> Subject: Re: Linux kernel updates and
> ip_crossover patch
>
>
>
>
>
> On Wed, Sep 24, Kaena Freitas wrote:
>
> >
> >
> >
> >
> > Hello Mehul -
> >
> > Sorry it has taken me a while to respond. We do not keep any code in CMVC.
> > All code we get from SuSE is on the ftp3 site along with all the source
> > RPMs. We do have internel CVS trees, but there is no guarantee that those
> > trees are current with the code we get from SuSE which is what your team
> > should be testing.
> >
> > As for the htx patch you've provided, I have copied SuSE on this email to
> > get their comments if it can be part of their distribution.
>
> Good morning,
>
> did you sent the patch to netdev@oss.sgi.com?
> What opinion have the network and iptables maintainers about this feature?
>
>
> > (See attached file: hxecom_patch)forgot to attach the patch.
> >
> >
> > e-mail: mehul.patel@in.ibm.com
> > IBM Global Services
> > Bangalore, India.
> > Tel: 091-80-5094160
> >
> >
> >
> >
>
> > Mehulkumar J
>
> > Patel To: Kaena Freitas/Austin
> /IBM
> > cc: Anil K Prasad/India/
> IBM@IBMIN, Daljeet
> > 23/09/2003 18:38 Maini/India/IBM@IBMIN
>
> > Please respond to From: Mehulkumar J Patel/
> India/IBM@IBMIN
> > Subject: Linux kernel updates
> and ip_crossover patch
> >
>
> >
>
> >
>
> >
> >
> >
> > Hi,
> >
> > We are HTX Team.
> > We get affected by changes in Linux kernel in a way where we have to update
> > our build environment
> > continuously. As of now we are doing so manually. But considering the
> > effort we are thinking of making
> > it automated.
> >
> > Can you please tell us if there is a fixed place from where we can sync
> > Linux kernel sources through
> > scripts. Or do you put Linux kernel sources in cmvc or any other version
> > control system.
> >
> > Also, we have an exerciser named "hxecom" which requires an external patch,
> > ip_crossover for hxecom
> > to work in single system test.
> > This patch helps us in sending packets destined to IP address on the same
> > machine without looping
> > back at IP layer. Packet actually goes out to hardware and thus we are able
> > to stress network cards.
> > For this patch to work, kernel should have been compiled with netfilter.
> > If netfilter is not enabled and ip_crossover patch is not applied, we end
> > up recompiling the whole
> > stuff and need to copy kernel and /lib/modules on all the test machines,
> > which is bit ugly.
> > Can you please include these two request from us in all p-series kernels ?
> >
> > I am attaching the patch here.
> >
> > best regards,
> > Mehul.
> > e-mail: mehul.patel@in.ibm.com
> > IBM Global Services
> > Bangalore, India.
> > Tel: 091-80-5094160
> >
> >
> >
>
>
>
> --
> USB is for mice, FireWire is for men!
>
> sUse lINUX ag, nÜRNBERG
>
>
--
Matthias Frühauf
Member of the spicy SuSE Linux PPC Team
------------------------------------------------------------
SuSE AG, Tel: +49-911-74053-658
Deutschherrnstr. 15-19, Fax: +49-911-74053-483
90429 Nuernberg Germany
--- Peace, Love and Linux ---
next prev parent reply other threads:[~2003-10-30 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 13:03 Linux kernel updates and ip_crossover patch Mehulkumar J Patel
2003-10-30 13:16 ` Matthias Fruehauf [this message]
2003-10-30 17:53 ` David S. Miller
2003-10-30 18:17 ` James R. Leu
2003-10-31 3:16 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 14:24 Mehulkumar J Patel
2003-10-27 16:16 ` Ben Greear
2003-10-27 16:34 ` Anil K Prasad
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=20031030131628.GL17431@suse.de \
--to=mfrueh@suse.de \
--cc=aprasad@in.ibm.com \
--cc=kaena@us.ibm.com \
--cc=mehul.patel@in.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=olaf@suse.de \
--cc=olh@suse.de \
/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).